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

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 =)

Regards,

Miguel Rentes

Software Engineer

Efacec Engenharia

ID - Gestão de Redes

Tlf: +351 22 940 3389

e-mail: miguel.rentes_at_efacec.pt <mailto:miguel.rentes_at_efacec.pt>

________________________________

From: Robert Graf-Waczenski [mailto:rgw_at_lsoft.com]
Sent: terça-feira, 26 de Agosto de 2008 15:11
To: Miguel Rentes
Cc: users_at_subversion.tigris.org
Subject: Re: Creating a complex tag with the list of files changed necessary for a bug correction

Miguel Rentes wrote:

Hi Robert,

At a given commit I have the complete list of files I had to change to correct a bug. After that I want a tag named "correction ABC" that has only the files/directories I had to change to correct that bug.

I don't think that such a tag would be possible, but that still depends on some things that i'm unclear about. First off, Subversion does not have a concept of tags. In subversion, tags are copies of parts of your repository with the additional semantics that you intend to never modify this copy again (the latter part is typically achieved via a pre-commit hook or mere developer discipline).

Maybe you should elaborate a bit about what you plan to do with the "tag" you are talking about, then we can tell you what subversion concepts and mechanisms are available to achieve what you plan to do.

Robert
Received on 2008-08-26 16:57:54 CEST