-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paola Attadio <[EMAIL PROTECTED]> writes:
> >>I can use the LocalKeyword, but I can't use Log in this definition. I
> >>don't have any problems with the others keywords. Let see,
> >> LocalKeyword=MyKeyword=Log give me a error with the commit action.
> >>
> >>
> >
> >Hmmm... yes, at present there is only support for
> >
> > LocalKeyword=<token>={ID|Header|CVSHeader}
> >
> >I suppose that should either be made clearer in the documentation, or
> >the number of possible expansions should be increased...
> >
> >fwiw: Lots of people who think they want $Log$ in their source file
> >later find it to be more trouble than it is worth when they are doing
> >branch merges amongst multiple releases...
> >
> >
> Its explain my problem. Is it possible that the <token> doesn't accept
> some characters, for example, "_"?
No. Look at src/rcs.c RCS_setlocalid() for how it is parsing the line.
Anything up to the next '=' sign that is a a valid character will be
okay. This allows for many iso-8859-1 characters to be in the new
keyword and includes the underscore ("_") characer in the allowed list
of characters..
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFBq2lQ3x41pRYZE/gRAlTgAKCpYjG8DjAM99X9TVnDHq/6tuvu1QCghOek
uiO+ro//DBHJuvAEeW+szYk=
=9izP
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
