[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: logs of revisions since release (repost)
From: |
Chuck . Irvine |
Subject: |
Re: logs of revisions since release (repost) |
Date: |
Wed, 12 Dec 2001 14:33:46 -0600 |
Larry,
Sorry for the repost, but I didn't get a specific response
from you on this, so I thought I would repost a shorter and
hopefully clearer message. Please see below. Thanks
Chuck
<deleted>
> >
> > 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
>
Thanks for the suggestion but either it's not working
or I am misunderstanding.
My problems are illustrated below. The lines prefixed
with "***" are my comments. Everything else is
a log of cvs command invocations.
My desired result is to print out revision logs for all
new revisions on my build branch:
**************** CVS Command Interaction Log ****************
*** First create a file and check it in to the trunk:
> 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 CVS command should not produce any revision logs
since,
*** by definition, there were no revision logs between 1.1 and 1.1.
*** I'm using revision "1.1" for both starting and ending tags to
*** account for the case where a file has no new revisions between
*** the start and end tag. 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
*** Update to the new 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
- Re: logs of revisions since release (repost),
Chuck . Irvine <=