Package: rcs
Version: 5.8.1-1
When using symbolic names, one being substring of another, RCS
now appears to somehow confuse the two. Consider, e. g.:
$ rlog -rfoo nh3ypimyfqowgqnkiza1dhx9ib
RCS file: RCS/nh3ypimyfqowgqnkiza1dhx9ib,v
Working file: nh3ypimyfqowgqnkiza1dhx9ib
head: 1.2
branch:
locks: strict
access list:
symbolic names:
foo_bar: 1.2
foo: 1.1
keyword substitution: kv
total revisions: 2; selected revisions: 1
description:
----------------------------
revision 1.2
date: 2013/04/29 16:06:52; author: jrh; state: Exp; lines: +1 -0
Added ‘bar’.
=============================================================================
$
That is, now that there's ‘foo_bar’, the ‘foo’ name appears to
be interpreted as ‘foo_bar’!
Cf. the behavior of rcs 5.7-25:
$ rlog -rfoo nh3ypimyfqowgqnkiza1dhx9ib
RCS file: RCS/nh3ypimyfqowgqnkiza1dhx9ib,v
Working file: nh3ypimyfqowgqnkiza1dhx9ib
head: 1.2
branch:
locks: strict
access list:
symbolic names:
foo_bar: 1.2
foo: 1.1
keyword substitution: kv
total revisions: 2; selected revisions: 1
description:
----------------------------
revision 1.1
date: 2013/04/29 16:05:14; author: jrh; state: Exp;
Initial revision
=============================================================================
$
The behavior of co(1) changes similarly across the versions.
--
FSF associate member #7257
head 1.2;
access;
symbols
foo_bar:1.2
foo:1.1;
locks; strict;
comment @# @;
1.2
date 2013.04.29.16.06.52; author jrh; state Exp;
branches;
next 1.1;
1.1
date 2013.04.29.16.05.14; author jrh; state Exp;
branches;
next ;
desc
@@
1.2
log
@Added ‘bar’.
@
text
@foo
bar
@
1.1
log
@Initial revision
@
text
@d2 1
@
