In what might be his last Joel on Software post (for awhile, at least) http://www.joelonsoftware.com/items/2010/03/17.html Summary: Early 2009: Joel disses DVCSes. His programmers switch from subversion to hg. Joel grumbles. His programmers develop an hg-related product. Joel takes a better look. Joel sees the light: Subversion controls versions, hg controls changes; this make merging much easier. Joel flips (his opinion): Switch now! Joel write hg tutorial: http://hginit.com/ It starts with "Subversion Re-education" for existing version-oriented system users and continue with "Ground up Mercurial" where new vcs users can start. It has several simple examples. Having gotten that far, I think this might be worth referencing in new dev docs. Terry Jan Reedy
On Thu, Mar 18, 2010 at 22:38, Terry Reedy <tjreedy@udel.edu> wrote:
Having gotten that far, I think this might be worth referencing in new dev docs.
Will do. I finally read hginit yesterday, after having seen people rave about it on twitter for a few weeks, and it's a very friendly introduction. Cheers, Dirkjan
Dirkjan Ochtman wrote:
On Thu, Mar 18, 2010 at 22:38, Terry Reedy <tjreedy@udel.edu> wrote:
Having gotten that far, I think this might be worth referencing in new dev docs.
Will do. I finally read hginit yesterday, after having seen people rave about it on twitter for a few weeks, and it's a very friendly introduction.
The key insight for me was the "manage versions" vs "manage change sets" distinction between a traditional VCS and a DVCS. I kind of knew that already, but that page expressed it really well. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia ---------------------------------------------------------------
On Fri, Mar 19, 2010 at 4:52 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Dirkjan Ochtman wrote:
On Thu, Mar 18, 2010 at 22:38, Terry Reedy <tjreedy@udel.edu> wrote:
Having gotten that far, I think this might be worth referencing in new dev docs.
Will do. I finally read hginit yesterday, after having seen people rave about it on twitter for a few weeks, and it's a very friendly introduction.
The key insight for me was the "manage versions" vs "manage change sets" distinction between a traditional VCS and a DVCS. I kind of knew that already, but that page expressed it really well.
Hi, Is Python-dev going to consider shifting their repo to mercurial/git instead of SVN? :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/aries.shuaib%40gmail.com
-- M. Shuaib Khan http://mshuaibkhan.blogspot.com
On Fri, Mar 19, 2010 at 04:59:38PM +0500, M. Shuaib Khan wrote:
Is Python-dev going to consider shifting their repo to mercurial/git instead of SVN? :)
http://mail.python.org/pipermail/python-dev/2009-March/087931.html The decision was made about a year ago. http://www.python.org/dev/peps/pep-0374/ http://www.python.org/dev/peps/pep-0385/ Oleg. -- Oleg Broytman http://phd.pp.ru/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
M> Is Python-dev going to consider shifting their repo to mercurial/git M> instead of SVN? :) Yes, Dirkjan has been working on it. My initial experience with hg as a quick way to revision control anything anywhere on a small scale ("hmmm, I should track changes to /etc/hosts... cd /etc ; hg init ; hg add hosts") worked quite well, but when I tried to use it for something where I was actually working collaboratively (my lockfile module) I managed to get my code/branches/heads/whatever completely f**ked up. I gave up and just went back to Subversion. Skip
On 3/19/2010 5:00 AM, Dirkjan Ochtman wrote:
On Thu, Mar 18, 2010 at 22:38, Terry Reedy<tjreedy@udel.edu> wrote:
Having gotten that far, I think this might be worth referencing in new dev docs.
Will do. I finally read hginit yesterday, after having seen people rave about it on twitter for a few weeks, and it's a very friendly introduction.
Having read further 'lessons', you might also want to note that the Python group workflow differs (and briefly how so) from that given as a possibility, assuming that it does. Terry Jan Reedy
On Fri, Mar 19, 2010 at 11:00 AM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
Having gotten that far, I think this might be worth referencing in new dev docs.
Will do. I finally read hginit yesterday, after having seen people rave about it on twitter for a few weeks, and it's a very friendly introduction.
I more like hands-on approach that does use real world workflow instead of academic examples. For example, tutorial like Ondrej Certik made for SymPy patches using Mercurial queues. http://docs.sympy.org/sympy-patches-tutorial.html It goes straight from the problem in SymPy development you'd like to resolve for yourself and then shows how Mercurial helps with it. If you have more time to dig - you may read a book or Joel series. -- anatoly t.
participants (7)
-
anatoly techtonik -
Dirkjan Ochtman -
M. Shuaib Khan -
Nick Coghlan -
Oleg Broytman -
skip＠pobox.com -
Terry Reedy