Re: Tagging changesets

On Fri, 2006-08-25 at 17:06 +0200, Holger Stratmann wrote:
> Use Beyond Compare or whatever to "mark" your
> changes as belonging to feature A or bug B before you commit. That's not
> so nice from a Subversion perspective, but at least you'd keep your
> "existing functionality" (i.e. a text editor?!) in those cases. I think
> the overhead for this is, was and will be significant, so it's much
> better to finish A before starting B if you really want to "track" it
> separately.

Or unless you have a strict policy of only allowing completed work to
be in the repository (in which case you should probably have branches
for ongoing work anyway), just commit the partly complete work on A
before changing anything for B, and say so in the commit message. You
are going to have to deal with things committed in multiple stages as
soon as someone makes a mistake or takes several tries to get something
finished anyway.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org