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

Re: Creating a complex tag with the list of files changed necessary for a bug correction

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Tue, 26 Aug 2008 11:10:09 -0400

Miguel Rentes wrote:
> The tag I want is just a copy of all the resources I had to modify in
> order to fix a bug at a given time.

That is a very odd way to use Subversion. A tag in Subversion is merely
a pointer to a given point in time in the repository, not like CVS where
tags are associated with a list of files.

Normally, you would commit all of those changes in a single commit and
thus that changeset would constitute what files were changed. If you
want to associate that changeset with a specific bug ticket, you would
add that bug ticket to the commit message (say if you were using
something like Trac).

Alternatively, you can develop a bugfix in a branch and when you are
complete, you merge it as a single commit (again associating that commit
with the bug ticket). The branch can be left as is for the other
developers to see or deleted once merged.



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-26 17:10:52 CEST

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

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