Thanks Gregor, I think I'm the only one in the dark, Dan just has to handle what I send him since I don't have commit privs, so, heretofore, I've been unsure of how CVS worked with the remote repository when I can't commit my own changes. Basically what I've been doing is just checking out a CVS snapshot every day or so, and to keep it up to sync with my private tree I manually diff it, then apply my changes to the new tree, sometimes fixing conflics, re-diffing against the new up-to-date version, and submitting the patch. Yes its sad but I developed on linux-kernel over the years and survived.
This is a lot of work sometimes but I've just not gotten used to using CVS
nor am I sure how it would work if I used CVS locally, not having commit
privs for
the master, then resyncing from the master. I'm used to SourceSafe or
similar
where I can checkout and lock files, but not distributed control systems
like
CVS.
Maybe some CVS gurus could enlighten me.
-Melvin Smith
IBM :: Atlanta Innovation Center
[EMAIL PROTECTED] :: 770-835-6984
(Embedded
image moved to "Gregor N. Purdy" <[EMAIL PROTECTED]>
file: 01/09/2002 03:23 PM
pic17700.pcx)
To: Dan Sugalski <[EMAIL PROTECTED]>
cc: Melvin Smith/ATLANTA/Contr/IBM@IBMUS, "David M. Lloyd"
<[EMAIL PROTECTED]>, Parrot Internals <[EMAIL PROTECTED]>
Subject: CVS Diff Options Suggestion [was: Re: Problem with MANIFEST
(missing io/io_unix.c)]
Dan, Melvin and Co. --
I find that if I've used cvs add and cvs remove for any added or removed
files, I can create a patch quite nicely from the root directory thusly:
$ cvs -q diff -NauR > ../foo.patch
YMMV.
Regards,
-- gregor
____________________________________________________________________
/ Inspiration >> Innovation >> Excellence (TM) \
Gregor N. Purdy [EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
8080 Beckett Center Drive #203 513-860-3570 vox
West Chester, OH 45069 513-860-3579 fax
\____________________________________________________________________/
[[EMAIL PROTECTED]]$ ping osama.taliban.af
PING osama.taliban.af (68.69.65.68) from 20.1.9.11 : 56 bytes of data.
>From 85.83.77.67: Time to live exceeded
pic17700.pcx
Description: Binary data
