--- In [EMAIL PROTECTED], [EMAIL PROTECTED] (Guus Leeuw) wrote:
> > -----Original Message-----
> > From: Fabrice Gautier [mailto:gautier@e...]
> > cvs -q diff -u -r > mypatch.txt
>
> You should read the Cederqvist manual.
>
> Try the command rdiff and you probably want to forget about
> the -u option (unidiff, which is not supported by old patch
> programs).
Well, I've read it quite a bit....especially where there was diff or
rdiff mentionned.
And rdiff always ask me for a module name and a revision number when
I just want a diff between a file in my working directory and a the
remote one it is based on.
A bit of Cederqvist readings about rdiff:
"Like the diff command, except it operates directly in the repository"
Well, you got it...
But anyway, the problem is a bug corrected in cvs 1.10.3
And reading Cederqvist didn't help to know why when you use a 1.10.5
client you still see the bug - the obvious answer I didn't figured
out was that the bug is in the server, and Cderqvist doesn't give a
clue about the diff being processed by the server (even on the
working file)
How and still another question I didn't see the answer in the
Cederqvist is how I produce a patch with a new file (ie: a file
present in the working copy but not the repository). May be it's
another bug of the cvs server, but -N doesn't work.
So If you have the page in the Cederqvist where there is an
answer....>:->
To be more general I don't think the Cederqvist handle the situation
of people who have only read access to the repository (at least the
free chapters).
Thanks
Fabrice
