info-cvs
[Top][All Lists]
Advanced

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

Re: logs of revisions since release


From: Colm Murphy
Subject: Re: logs of revisions since release
Date: Fri, 07 Dec 2001 11:53:52 +0000
User-agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-GB; rv:0.9.4) Gecko/20011019 Netscape6/6.2

Hi Chuck,

I think that there is a bug in cvs log (and cvs rlog) in 1.11.1.p1 in that it returns information on all the files in the module/directory you specify and not just the ones with the tags you specify.

This is probably what you are seeing.

Colm A

address@hidden wrote:


-----Original Message-----
From: larry.jones [mailto:address@hidden
Sent: Thursday, December 06, 2001 4:03 PM
To: Chuck.Irvine
Cc: info-cvs; larry.jones
Subject: Re: logs of revisions since release


address@hidden writes:

For each release, we tag our repository, so say I have tags
R1 and R2.
Passing "-rR1:R2" to the log command won't work because
this will give
me the log message for the release corresponding to R1. "-rR1::R2" won't work because this doesn't give me a log
message for
R2, which I need.
-rR1::R2 -rR2

-Larry Jones

Wow, how existential can you get? -- Hobbes



Thanks for the suggestion but I'm sorry to say that it
doesn't seem to work. Problems are illustrated below. Lines prefixed with "***" are my comments. Everything else is cvs command execution i/o (keep in mind that my goal is
to print out revision logs for all new revisions on my
build branch):



touch foobar
cvs add foobar

cvs server: scheduling file `foobar' for addition
cvs server: use 'cvs commit' to add this file permanently

cvs ci -m "first foobar ci" foobar

RCS file: /cm/cvsroot/scratch/foobar,v
done
Checking in foobar;
/cm/cvsroot/scratch/foobar,v  <--  foobar
initial revision: 1.1
done
*** The following should not produce any revision logs since
*** there were no revision logs between 1.1 and 1.1. *** However the command invocation gives the log for r1.1.

cvs log -r1.1::1.1 -r1.1 foobar


RCS file: /cm/cvsroot/scratch/foobar,v
Working file: foobar
head: 1.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;     selected revisions: 1
description:
----------------------------
revision 1.1
date: 2001/12/06 22:44:36;  author: ccu1258;  state: Exp;
first foobar ci
===========================================================
*** Now create a branch on foobar

cvs tag -b br foobar

T foobar
*** Check in a new version to the trunk just to see
*** what the effect is.

echo test >> foobar
cvs ci -m "second ci to trunk" foobar

Checking in foobar;
/cm/cvsroot/scratch/foobar,v  <--  foobar
new revision: 1.2; previous revision: 1.1
done
*** Update to the previously created branch

cvs update -r br foobar

U foobar
*** Invoke the following to see all revision logs
*** on branch "br" between r1.1 and r1.1. Keep in
*** mind that since foobar hasn't changed on the
*** branch, two subsequent branch tags would *** point to the revision branched on.

cvs log -r1.1::1.1 -r1.1 foobar


RCS file: /cm/cvsroot/scratch/foobar,v
Working file: foobar
head: 1.2
branch:
locks: strict
access list:
symbolic names:
        br: 1.1.0.2
keyword substitution: kv
total revisions: 2;     selected revisions: 1
description:
----------------------------
revision 1.1
date: 2001/12/06 22:44:36;  author: ccu1258;  state: Exp;
first foobar ci
============================================================
*** Again, no revision logs should have been printed, this
*** time since no revisions have been made on the trunk






reply via email to

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