[EMAIL PROTECTED] writes:
>
> 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
I didn't have anything to say -- you're right, my suggested method
doesn't work when ther
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
> >
> > For each release, we tag our repository, so say I have tags R1 and
R2.
> > Passing "-rR1:R2" to t
Thanks Larry.
rlog is now working as expected.
Colm A
Larry Jones wrote:
> Colm Aengus Murphy writes:
>
>>When I run "cvs rlog -rMyTag:: directory".
>>
>>Everything works fine until it gets to a file that doesn't contain
>>MyTag. It gives a warning and then dies with "Terminated with fatal
Colm Aengus Murphy writes:
>
> When I run "cvs rlog -rMyTag:: directory".
>
> Everything works fine until it gets to a file that doesn't contain
> MyTag. It gives a warning and then dies with "Terminated with fatal
> signal 11 "
I've checked in a fix for this problem.
-Larry Jones
OK, there
Colm Aengus Murphy writes:
>
> Everything works fine until it gets to a file that doesn't contain
> MyTag. It gives a warning and then dies with "Terminated with fatal
> signal 11 "
>
> Any ideas ?
It seems I overlooked one or two cases in my fix. I'm working on it...
-Larry Jones
This gam
Hi Larry,
I've downloaded and installed the development version.
When I run "cvs rlog -rMyTag:: directory".
Everything works fine until it gets to a file that doesn't contain MyTag.
It gives a warning and then dies with "Terminated with fatal signal 11
"
Any ideas ?
Cheers
Colm A
Larry J
Colm Murphy writes:
>
> "cvs rlog -rMyTag:: directory"
>
> returns the RCS logs for file1 since MyTag along with all of the RCS
> logs for file2 with a warning that file2 doesn't contain the tag MyTag.
>
> I would expect that if a file doesn't contain the tag then no RCS logs
> are returned.
Hi Larry,
It looks like I have mis-understood the purpose of cvs log.
That said I still have a problem with its operation.
Say I have a directory with two files: file1 and file2.
file1 contains MyTag and file2 does not.
"cvs rlog -rMyTag:: directory"
returns the RCS logs for file1 since MyTag
Colm Murphy writes:
>
> 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.
That's not a bug -- it's the way it's designed. The -r and -d opt
:
>
>>-Original Message-
>>From: larry.jones [mailto:[EMAIL PROTECTED]]
>>Sent: Thursday, December 06, 2001 4:03 PM
>>To: Chuck.Irvine
>>Cc: info-cvs; larry.jones
>>Subject: Re: logs of revisions since release
>>
>>
>>[EMAIL PROTECTED] writes
> *** 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: /c
> -Original Message-
> From: larry.jones [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 06, 2001 4:03 PM
> To: Chuck.Irvine
> Cc: info-cvs; larry.jones
> Subject: Re: logs of revisions since release
>
>
> [EMAIL PROTECTED] writes:
> >
[EMAIL PROTECTED] 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
13 matches
Mail list logo
