[Python-Dev] PEP: Migrating the Python CVS to Subversion
abo at minkirri.apana.org.au
Tue Aug 9 03:13:10 CEST 2005
On Mon, 2005-08-08 at 17:51, Trent Mick wrote:
> [Donovan Baarda wrote]
> > On Mon, 2005-08-08 at 15:49, Trent Mick wrote:
> You want to do checkins of code in a consisten state. Some large changes
> take a couple of days to write. During which one may have to do a couple
> minor things in unrelated sections of a project. Having some mechanism
> to capture some thoughts and be able to say "these are the relevant
I don't need to checkin in a consitent state if I'm working on a
seperate branch. I can checkin any time I want to record a development
checkpoint... I can capture the thoughts in the version history of the
> source files for this work" is handy. Creating a branch for something
> that takes a couple of days is overkill.
> The alternative being either that you have separate branches for
> everything (can be a pain) or just check-in for review (possibly
It all comes down to how painless branch/merge is. Many esoteric
"features" of version control systems feel like they are there to
workaround the absence of proper branch/merge histories.
Note: SVN doesn't have branch/merge histories either.
Donovan Baarda <abo at minkirri.apana.org.au>
More information about the Python-Dev