> -----Original Message-----
> From: Brad Appleton [mailto:brad@bradapp.net]
> Sent: Friday, March 12, 2004 4:44 PM
> To: N. Thomas
> Cc: users@subversion.tigris.org
> Subject: Re: branching several times a day (was Re: Sourcesafe user
> needs primer on branching source control)
[...]
> If you created a branch-per-task, then the branch is a grouping
> mechanism for your resulting change-set for that task. Does SVN
> already have a grouping mechanism (independent from branches)
> that identifies what my change-set was and all the participating
> files and file-changes from the beginning-to-end of my task?
>
> If it has that (I had the impression it does), then do I need
It does as long as you get it right on the first commit. After that it
becomes muddy (and you end up having to grab multiple revisions to represent
all of the changes for your task. So it's still technically possible, IMHO
just not as practical or elegant as having a branch that ONLY contains
changesets related to the task at hand. Unless of course you perform updates
from the trunk into the branch, at which point I would agree that creating a
branch may very well be overkill.
cheers
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 12 22:54:58 2004