[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn checkpoint: r27213 - checkpoints/relative-externals

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-10-16 17:04:39 CEST

"Ben Collins-Sussman" <sussman@red-bean.com> writes:
> So now you're using svnmerge.py to carefully keep your 'checkpoint' in
> sync with trunk. At this point, how is it any different from a
> feature branch? Is it just the fact that you don't want to write
> structured log messages or have people review the code?
> I guess I can understand using /checkpoints as a general anarchy
> dumping-ground to make backups of patches, but this sort of blurs the
> line. Why not just make a feature branch and ask folks not to review
> it yet?

Well, you doesn't always know when you start something how long it's
going to take, or how many commits, etc.

I think it's fine to move from /checkpoints into /branches, when
something turns out to need a typical feature branch.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 16 17:04:49 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.