[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: cvs "grouping" feature

From: Brouwer, Marcel
Subject: RE: cvs "grouping" feature
Date: Wed, 31 Aug 2005 07:21:34 +0200

Can you give me some information about the "commit ids" features functionality 
and when it will be released?
I'm also looking for some 'functional' grouping.
We are working with softwarereleases which will be released at a certain point 
in time. And it is not clear 
if al change request will be in it. (Some not finished jet, not passed 
acceptance test,or QC)
But also to propagate some change requests from development to test before the 
complete release will 


-----Oorspronkelijk bericht-----
Van: Derek Price [mailto:address@hidden
Verzonden: dinsdag 30 augustus 2005 20:07
Aan: address@hidden
CC: Mark D. Baushke; Frank Hemer
Onderwerp: Re: cvs "grouping" feature

Excuse me.  Mark Baushke pointed out to me that commitids are currently
being created by 1.12.12 but that they can not yet be accessed as tags. 
Frank Hemer did much of the necessary work already but it is still stuck
on the `newtags' branch and not on the trunk.



Derek Price wrote:

>Starting with release 1.12.12, CVS has "commit ids" which basically do
>what you are asking for.  They are automatically attached to each
>revision of each file involved in a commit, and are accessed like tags.
>address@hidden wrote:
>>I recently started using cvs - setting up practice repositories -
>>updating, commiting etc.  I have found it to be very rodust and
>>complete.  however, there is one feature that I have seen in other
>>commercial SCMs that I cannot fgure out how to do in CVS.
>>How can I "group" files that are spread throught the repositpry to be
>>committed or rolled back together?
>>Meaning - if I have to edit a few files to implememnt a particular
>>change, I want them to be comitted together, but I may be working on 5
>>different changes at once.  Do I have to remember which files are
>>involved and commit them together, or is CVS able to keep track of
>>which files are involved in which change as I'm working on them?  I'm
>>thinking this can be done by tagging?...
>>Info-cvs mailing list

Derek R. Price
CVS Solutions Architect
Ximbiot <>
v: +1 717.579.6168
f: +1 717.234.3125

reply via email to

[Prev in Thread] Current Thread [Next in Thread]