[Top][All Lists]

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

RE: Check in and out a file.

From: Jim.Hyslop
Subject: RE: Check in and out a file.
Date: Wed, 19 May 2004 15:03:34 -0400

address@hidden wrote:
> "Jim.Hyslop" <address@hidden> wrote in message 
> news:<address@hidden>...
> > address@hidden wrote:
> > > address@hidden (Larry Jones) wrote in message 
> > > 
> <>
> Uh no, you must think I did not read the manual. In fact, I had read
> the manual a few times but could not get answer from there.
Please re-read section 3.5.2 - it will tell you everything you need to know.
Pay particular attention to the "format strings" section.

Well, actually, maybe there's something not quite clear there. The formatted
string is passed to your script. So, if you have an entry like:

ALL             $CVSROOT/CVSROOT/ %s

then the script will be passed a list of all file names as
its first parameter.

> From what I understand, the manual is only good for check out the
> recently checked in file.
No, that is _one_ specific example of the kinds of things you _can_ do with
loginfo. As the documentation says, the limit is your imagination.

> What I want is one a file is checked in, I
> want to check out the file and append the filename with a revision #.
> For example, if five developers check in five different copied of
> abc.c at very short delay. I expect to check out abc.c file and rename
> them as abc.c.1, abc.c.2, abc.c.3, abc.c.4 and abc.c.5 respectively in
> a particular directory.
Actually, why would you want to do that? It seems rather redundant.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (
Columnist, C/C++ Users Journal (

reply via email to

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