[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Update Behaviour

From: Greg A. Woods
Subject: Re: CVS Update Behaviour
Date: Sun, 24 Feb 2002 15:52:09 -0500 (EST)

You're spreading F.U.D. and untruths again Paul.

[ On Friday, February 22, 2002 at 20:51:55 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
> There's just one little problem with this:  "cvs log" only works when
> a file is in your sandbox.  If it's been removed and committed, then
> you must do something like "cvs rlog `cat CVS/Repository`/oldfile.c | less".

That's not true.  You are (still) using an old or broken or otherwise
buggy version of CVS.

> But that only works if the file was renamed in the same directory, not
> if it was moved to another directory.

This style of usage works just fine for me:

        cvs log ../old-dir-path/oldfile.c

>  In this latter case, you need to
> know where in the repository the RCS file sits, and that info isn't
> usually available without some effort, particularly if the module isn't
> defined trivially in the modules database.

Yes it is.  It's in the commit message written automatically by
something like my tiny simple little wrapper script.

> This exercise also doesn't consider the implications of doing the "cvs add"
> part in a sandbox that has been updated with a different branch than the
> original file.

That's because doing such a stupid thing is outside the bounds of
defined usage for CVS -- you really should only have one complete and
coherent sandbox, all checked out on only one branch if you're using
branches.  Anything and everything else may lead to undefined behaviour.

                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]