|
From: <gor...@bl...> - 2002-05-13 15:48:22
|
rwi...@at... wrote:
[SNIP]
> > It still bothers me that I _could_ make modifications
> to (say) the unix
> > tree but it appears that this can't be helped. Perhaps
> a good line in
> > the policy document would be to state that you "Never,
> NEVER do a 'cvs
> > commit' from the platforms directory but only from
> your platform branch
> > (win32, unix, Mac, Acorn, Cross)". I've been using
> this policy for me
> > already and so far it turns out to be a good practical
> rule.
>
> Heh. This is what I did this morning for the changes,
> but I had to re-checkout the toplevel to add
> osExports.c. Of course, I had done a 'cvs diff squeak',
> first, to verify that I was only commiting the files I
> had planned on commiting.
A good rule is to do a "cvs update" first on the same level that you
intend to commit.
The update will tell you what files are modified "M" and that will be
committed.
You can also then see if other people have just committed stuff ("P"/"U"
etc) that you should take into account before committing.
> Are the aliases I had defined in the CVSROOT/modules
> file a good idea? It may be better to checkout the
> explicit subtrees (Cross and unix in my case).
No, they are fine IMO.
regards, Göran
|