[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: Robert Graf-Waczenski <rgw_at_lsoft.com>
Date: Tue, 26 Aug 2008 17:05:58 +0200

Miguel Rentes wrote:
> Hi Robert,
> 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. Having this tag is a good
> mechanism so that any developer can know what I had to change to
> correct a given bug and can also know that in a given URL there's a
> complete set of files that corrected that particular bug. We have a
> team that is responsible to manage what our clients want in their
> software and what bugs they want to get corrected in a number of
> different releases. So, having this tag is also useful for this team
> that only has to see at what I have in the tag and integrate it in our
> software. As an example, suppose I had to correct folderA/file1.c and
> folderB/file2.c. In this case I would want to have a tag with only
> those two folders, folderA and folderB, with file1.c and file2.c in
> those folders, which fixed a known bug.
> Hope this example showed what I want for the tag =)

So what you want is not a tag, plain and simple. Compiling a set of
files / folders which contains exactly those that were affected in a
given revision should be possible after the fact by looking at the
revision that your commit created. I guess that some of the scripting
gurus on this list can help you how to accomplish that.

Received on 2008-08-26 17:10:35 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.