bug-cvs
[Top][All Lists]
Advanced

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

Re: cvs log -rtag_at_base_of_branch::tag_on_branch fails


From: Veda Larson Palmer
Subject: Re: cvs log -rtag_at_base_of_branch::tag_on_branch fails
Date: Fri, 2 Aug 2002 15:04:47 -0700 (PDT)

> Anyhow, could you try the development version of CVS and let me know
> if it works for you?

I tried the anonymous CVS pserver to get the source but unfortunately
my company's firewall is currently blocking port 2401.  Is there any
other way to get an appropriate development version?  IT said that I
could submit a request form to use the port but they won't be able to
get to it until next week.

Thanks,
-Veda

-----Original Message-----
Date: Fri, 02 Aug 2002 08:56:26 -0400
From: Derek Robert Price <address@hidden>
To: Veda Larson Palmer <address@hidden>
CC: address@hidden, address@hidden
Subject: Re: cvs log -rtag_at_base_of_branch::tag_on_branch fails

Veda Larson Palmer wrote:

>Hi Derek,
>
>I see what you mean about diff vs log, but my v1_0 is definitely an
>ancestor of v1_1 (case 1) - we defined branch1 to be rooted at v1_0.
>v1_0 is conceptually on the same branch as v1_1 - it's just at the
>base.  This is analogous to the example in the manual:
>
>http://www.cvshome.org/docs/manual/cvs_5.html#SEC54
>
>cvs rtag -b -r v1_0 branch1 ...
>
>------Trunk-----------v1_0-------------------------
>                         \
>                          \---branch1-----v1_1-------v1_2
>
>So, the command "cvs log -N -rv1_0::v1_1 ..." to get logs for changes
>between v1_0 and v1_1 should be well defined.  I would think that
>anyone who uses branches for maintenance releases would want to do
>this to generate changelogs.  Is this the way to do it or is there a
>better way?  How do you guys generate changelogs?
>
>Thanks,
>-Veda
>  
>

Hmm.  The news item in the NEWS file has this happening between 1.11.1pq 
and 1.11.2:

> Changes from 1.11.1p1 to 1.11.2:

[ . . . ]

> * The interpretation of revision ranges using :: in "log" and "rlog"
> has changed: a::b now excludes the log message from revision a but
> includes the log message from revision b.  Also, revision ranges that
> cross branch points should now work.


but I just double-checked the tags and it looks like Larry didn't make 
this change until after 1.11.2.

> cvs1-11-2: 1.73

[ . . . ]

> ----------------------------
> revision 1.74
> date: 2002/04/19 18:03:59;  author: scjones;  state: Exp;  lines: +73 -22
> * log.c (log_expand_revlist): First cut at code to allow logging
> between a revision and *any* ancestor, not just one explicitly on
> the same branch (e.g., from 1.1 to 4.1.2.3.6.1).
> ----------------------------
> revision 1.73
> date: 2002/03/17 20:13:59;  author: scjones;  state: Exp;  lines: +45 -26
> * log.c (cvslog, log_fileproc): Add -S option to suppress head or
> file name if no revisions selected.
> * sanity.sh (log): New tests for above.
> ----------------------------
>

Hmm.  Half of the change mentioned in the NEWS shows up in rev 1.72. 
 Anyhow, could you try the development version of CVS and let me know if 
it works for you?

Derek

-- 
                *8^)

Email: address@hidden
Public key available from www.keyserver.net - Key ID 5ECF1609
Fingerprint 511D DCD9 04CE 48A9 CC07  A421 BFBF 5CC2 56A6 AB0E

Get CVS support at http://ximbiot.com
-- 
I will not charge admission to the bathroom.
I will not charge admission to the bathroom.
I will not charge admission to the bathroom...

          - Bart Simpson on chalkboard, _The Simpsons_



reply via email to

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