| Re: [stellation-res] Repository shadowing and problem resolutions |
On Sat, Jul 20, 2002 at 06:58:07PM -0400, Mark C. Chu-Carroll wrote: > > Could you please put a "ChangeLog" file and manually record there every > > syncronization? So we can make sure we talk about the same repository? > > > > This is actually something I've been thinking about: what's really the best > way of maintaining a strong relationship between the two repositories? It's > hard with CVS, because there isn't a great way of recording project > versions in CVS. > > The changelog is one route: to say that the CVS checkin at time X corresponded > to Stellation component version Y. > > The other route is to use CVS tags to label things in the CVS repository > as corresponding to a particular repository version. The catch is, between > the four subproject components, we're talking about creating *hundreds* of > tags over the next couple of months, before we get to the point where > we self-host on eclipse.org. I don't know how well CVS and Eclipse will cope > with that volume of tags. > > I tend to actually prefer the tag approach, because a version tag > in CVS does correspond roughly to a project version in Stellation. If the info is in a ChangeLog, I can do a 'head ChangeLog' and know instantly where am I. How can I do that with CVS tags? I know how to set tags and how to retrieve a certain revision based on tag. Can I inquire: "what is the latest tag on the files in this sandbox/workspace" ? florin -- "If it's not broken, let's fix it till it is." 41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
Attachment:
pgpROGS02SsjB.pgp
Description: PGP signature