info-cvs
[Top][All Lists]
Advanced

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

Re: new feature.


From: Jim
Subject: Re: new feature.
Date: Mon, 24 Mar 2003 17:25:40 -0800

>
> The general recommended CVS usage model is that the repository be
> considered a whole entity. Thus, you tag the entire repository the way
> it should be for a particular release, whether it be a full release, or
> a partial delta.

I *think* you could define a module as having parts of all modules and then
tagging that single module would tag everything in the CVS tree...
http://www.cvshome.org/docs/manual/cvs_18.html#SEC157

C.1.1 Alias modules
 ...  as if the list of names aliases had been specified instead. aliases
may contain either other module names or paths. .....
>
> Extra tags on files cost almost nothing, and by properly maintaining
> your tags, you can re-generate your deltas trivially using "cvs diff
> -rtag1 -rtag2", which will generate no output for files that have not
> changed between tag1 and tag2.
>
> Is this something you're already doing with another revision control
> system? I can't think of any commonly used revision control system that
> does the sort of thing you're asking - at least, not ClearCase or
> Perforce, which are the other two I've used extensively.
>
> I'd say it's a lot more error-prone to do selective tagging correctly
> than tagging the entire repository.  CVS makes it simple to do things
> another way:
>
> * You keep a "build workarea" where you build and test your product. You
> can update any single or multiple files you need to fix problems you
> find during integration and testing. Or branch the files you want to
> modify.
> * When you're satisfied that the product built from your build area is
> release-ready, you tag it from the build area, which automatically tags
> the versions of the files that you have worked with in that build area.
>
>
> > -----Original Message-----
> > From: Marc Tessier [mailto:address@hidden
> > Sent: Monday, March 24, 2003 3:13 PM
> > To: Shankar Unni
> > Subject: RE: new feature.
> >
> >
> > I would like to see a feature to extract the most recent
> > revision of a file from a list of TAGs specified as a
> > parameters. Like  Tag A B C  and the file rev in A is 1.10
> > and in C it's 1.12   so If a do a checkout or export of TAG A
> > B and C   I will get the most recent file that is 1.12 from TAG C.
> >
> > Some people work with CVS by tagging all the files but in my
> > case I just want to work with delta. I do not need to resend
> > to my people all files  just need to send them delta so my
> > packages are small all the time.
> >
> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden
> > Behalf Of Shankar Unni
> > Sent: Monday, March 24, 2003 1:33 PM
> > To: 'CVS Mailing List'
> > Subject: RE: new feature.
> >
> >
> > Marc Tessier opined:
> >
> > > I would like to know where is the better place to ask new
> > > feature to be added to CVS? Is there any mailing list or web
> > > page to do so?
> >
> > Well, this is as good a place as any. Would you like to
> > describe the feature you'd like to see?
> > --
> > Shankar
> >
> >
> >
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> >
> >
> >
> >
>
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs





reply via email to

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