Frank A. Christoph writes:
>
...
>
> I tried "cvs diff" from the fptools/ghc, but it doesn't seem
> to work for me. I get a series of messages:
>
> cvs server: Diffing .
> cvs server: Diffing compiler
> cvs server: Diffing compiler/absCSyn
> ...
>
> but no diffs. Having done that, I wondered if maybe there had
> been no recent changes, but when I do "cvs update" I see a
> few changes:
>
..
>
> What am I doing wrong?
>
'cvs diff -r HEAD' is your friend.
> Sigbjorn Finne wrote:
> >Assuming you know the date at which you checked out a copy,
> >something like the following should do the trick:
> >
> > cvs diff -D 01/30/99 -r HEAD
> >
> >This requires you to have two copies of your CVS tree
> >though, the off-line one and one you can use to invoke
> >'cvs diff's from.
>
> Hm, OK, but what happens if there were multiple updates to
> the tree at Glasgow on that date, and my copy of it was not
> the last one? (Say there were updates at 4pm and 7pm, and I
> checked out my tree at 5pm.)
The date can also include the time of day (see CVS docs)...
anyway, this is not a problem for you since you're using anoncvs,
which is only updated once every 24 hours (each 'night' at 22:00
GMT or so.)
> In fact, I don't see why I need a local copy of the tree at
> all. If I haven't changed the tree, then it should be equal
> to an old version of the one at Glasgow, so shouldn't I be
> able to generate a patch file just by supplying two version
> identifiers, and having the CVS server compute the
> differences locally at Glasgow? The thing I don't understand,
> I guess, is how to determine the version identifier for my
> tree. (Here's my situation: I have a GHC snapshot on my
> computer at home, but I typically access the Glasgow CVS
> server from work. I want to generate a patch file every few
> days so that I can fit the changes onto a floppy, carry it
> home and apply them manually to keep the tree up to date.)
>
afaik, cvs doesn't let you do that - you need to be within
a CVS tree in order to issue these commands.
--Sigbjorn
