info-cvs
[Top][All Lists]
Advanced

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

no actually non-branch deltas show up in 'cvs log -rBRANCH' output


From: Teala Spitzbarth
Subject: no actually non-branch deltas show up in 'cvs log -rBRANCH' output
Date: Thu, 19 Jul 2001 17:22:59 -0700

I thought the attic files accounted for it, but I've just 
run a full "cvs log -rBRANCHNAME" on our tree, with a perl script to
parse 
out the 'dead' files - and we still get something like 30-40
files that have been modified today, and are *not* on the branch, but
get listed as selected revisions. I.e. see output for files like
below..... 
They aren't attic files and they are not on the branch! Some of the
files 
are initial submissions, but not all, none of them appear to have
revisions 
on the branch in addition to the changes on Main. Why these files get
selected 
with the -r flag to log is a mystery to me.... so now I'm using perl to
strip out
any log output that doesn't have a branch revision, and can finally
get something meaningful for our change lists.

If anyone knows why I would still be interested for posterity -
though I have an adequate work around for now.

Thanks
Teala

(example of Non-branch file being selected with a cvs log -rBRANCHNAME
command)
========================================================================
=====

RCS file: /cvsroot/a/src/TreeComponent.java,v
Working file: a/src/TreeComponent.java
head: 2.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 1;     selected revisions: 1
description:
----------------------------
revision 2.1
date: 2001/07/19 19:29:43;  author: hops;  state: Exp;
Make TreeComponent base class....
========================================================================
=====

-----Original Message-----
From: Teala Spitzbarth 
Sent: Thursday, July 19, 2001 2:38 PM
To: David Taylor; address@hidden
Subject: RE: extracting log information for branch changes?


David,

Thanks very much for your reply - it was indeed the fact that Attic 
files were being included in the log output for the branch that 
was confusing me. We had enough deleted files in the tree that the
plethora 
of 'non-branch' files showing up for 'selected revisions' was making me 
think that all files were being selected.

Cheers!
Teala

-----Original Message-----
From: David Taylor [mailto:address@hidden
Sent: Wednesday, June 06, 2001 8:07 PM
To: Teala Spitzbarth
Subject: Re: extracting log information for branch changes?


Hello -

Although you posted your query months ago, I  didn't see a response
posted. So just in case...

If TAG is the branch tag, then:

cvs log -rTAG:

should do the trick. That is, it will select only changes that have been
made on the TAG branch and 'selected revisions' would only be greater
than 0 if the file in question actually has a branch'd revision (eg
2.4.2.1).

The one exception, unfortunately, is that it seems to select *all*
revisions of Attic files.

hope this helps,
d.l. taylor

extracting log information for branch changes?

Teala Spitzbarth address@hidden
Fri, 20 Apr 2001 16:31:59 -0700

    Previous message: One file in several modules?
    Next message: One file in several modules?
    Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]



Hi folks,

Is there a straightforward way with 'cvs log' to select
only changes that have been made on a branch?
I mean where 'selected revisions' would only be greater
than 0 if the file in question actually has a branch'd revision (eg
2.4.2.1)

I have tried using all the various permutations of=20
cvs log -rbranch =20
cvs log -rbranch.
cvs log -rTAG1:TAG2 (where TAG1 is the TAG at the head of the branch and

        TAG2 is a later tag for a build of interest)
cvs log -rTAG1:TAG2 (where TAG1 is a tag on the branch, after the
beginning of the branch
        and TAG2 is a later tag on the same branch)
cvs log -rbranch -d date1<date2

and all of these result in log output where all files in our tree are=20

'selected revisions'.  Am I missing something, or does log output
always land up selecting all revisions of files that are on the=20
branch period?

Also presence of CVS revision ids of the form x.x.0.x next to a Branch
tag=20
in the log output makes it seem at first glance that more files were
modified
on the branch than really were....=20

Thanks much
Teala Spitzbarth



_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



reply via email to

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