django-reversion - Google Code
http://code.google.com/p/django-reversion/

"Version control for Django models"

Reversion is an extension to the Django web framework that provides comprehensive version control facilities.

Revision control for Django models. Might be useful for those times when I forget/neglect to add to SVN.

Uma história para descrever o funcionamento interno do Git

simple, but extremely powerful system. Most people try to teach Git by demonstrating a few dozen commands and then yelling “tadaaaaa.” I believe this method is flawed. Such a treatment may leave you with the ability to use Git to perform simple tasks, but the Git commands will still feel like magical incantations. Doing anything out of the ordinary will be terrifying. Until you understand the concepts upon which Git is built, you’ll feel like a stranger in a foreign land.

"The following parable will take you on a journey through the creation of a Git-like system from the ground up. Understanding the concepts presented here will be the most valuable thing you can do to prepare yourself to harness the full power of Git. The concepts themselves are quite simple, but allow for an amazing wealth of functionality to spring into existence. Read this parable all the way through and you should have very little trouble mastering the various Git commands and wielding the awesome power that Git makes available to you."

'The following parable will take you on a journey through the creation of a Git-like system from the ground up.'

"Git submodules are implemented using two moving parts: the .gitmodules file and a special kind of tree object. These together triangulate a specific revision of a specific repository which is checked out into a specific location in your project."

Fraser Speirs explains the difference between good old svn:externals and git submodules.

to rebase or to merge, that is the question.

intro to rebase

Rebase helps to cut up commits and slice them into any way that you want them served up, and placed exactly where you want them. You can actually rewrite history with this command, be it reordering commits, squashing them into bigger ones, or completely ignoring them if you so desire.

Quick, clear, simple guide to the way Mercurial handles branching.

useful

brilliant!

Quick mercurial guide for svn users

Version control (compatible with Mercurial) written in Ruby.

Mercurial ported to Ruby with very easy customization.

Amp is unlike any other VCS software to date. Amp's novel command system gives you the flexibility to customize and personalize the way you develop software. Create in your own workspace with full Mercurial compatibility, and no external dependencies.

▍ ★∴ 　　　．．．．▍▍．..．█▍ ☆ ★∵ ..../ 　　　◥█▅▅██▅▅██▅▅▅▅▅███◤ 　　　．◥███████████████◤ 　～～～～◥█████████████◤～～～～ www.nikes-jordan.com , instant online Paypal payment! TT Assuring good quality, Coupons and feebies! Don't miss out! Jordan，AF1，Nike , RunningShoes, Sneakers, Dunks $40 Brand Jeans: $ 38 Brand sunglasses, $18 Brand Caps/Hats: $ 18 Brand Belts: $ 28 UGG boots：$ 55 Free Shipping, Retail and wholesale! Payment options: Paypal , TT, Westunion www.nikes-jordan.com

I still run into people lambasting git for the concept of the index from time to time. It seems strange and superfluous to users of other VCSs – like a speed bump that serves no purpose. Why not just commit the changes in the working copy? This perception is understandable; when I first heard of git, back as a Subversion user, I was one of these people. How times and minds change. Today, I use it and rely on it so much that I can’t imagine moving to any other VCS that doesn’t have this concept. (And none of the contemporary contenders do.) Because of this, I keep responding to such criticism, repeating myself. I figured I should put my explanation down somewhere where I can point people to.

by @martinfowler

Joel @Spolsky likes Mercurial so much he wrote a tutorial: http://www.joelonsoftware.com/items/2010/03/17.html and http://hginit.com/ – Guido van Rossum (gvanrossum) http://twitter.com/gvanrossum/statuses/10693471706

"If you come at Mercurial with a Subversion mindset, things will almost work, but when they don’t, you’ll be confused, unhappy, and unsuccessful, and you’ll hate Mercurial. Whereas if you free your mind and reimagine version control, and grok the zen of the difference between thinking about managing the versions vs. thinking about managing the changes, you’ll become enlightened and happy and realize that this is the way version control was meant to work."

on how to think distributed....

Beginners guide. Very good introduction.

starter for using a central git repo

Looks like the model we should use to start our migration away from svn.

はてながgitに移行した話のセッションメモ。

新はてなブックマーク * ユーザ数：21.6万 * PV数：790万PV/日 * サーバ台数：50台 * 2008年11月にリニューアル * 開発期間約9か月 o 最初の4ヶ月くらいは、id:naoyaさんが1人で 旧システムの問題点 * 保守性・拡張性 * テスタビリティ * 他サービスとの密結合

gitよいよい