bug-cvs
[Top][All Lists]
Advanced

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

Re: $Log$ substitution in binary files.


From: Derek Robert Price
Subject: Re: $Log$ substitution in binary files.
Date: Fri, 10 Sep 2004 11:35:24 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark D. Baushke wrote:

> However, I'd suggest that in the case where the search back to find a \n
> for <number-of-characters> does not find it, that cvs falls back to the
> old-style RCS 'comment' character as the prefix to use by default.


In addition to the 256 character limit?

> In theory, a prefix of 1024 characters could be set if the user did a
>
>   cvs admin -c '<how-ever-many-characters-is-desired>' filename
>
> to explicitly set a prefix that exceeds your <number-of-characters>
> heuristic limit...


True.  I usually do dislike artificially imposed limits even when I
can't think of a good reason why a comment leader larger than 20
characters would be useful...  so a workaround would be nice...  Hrm...

Okay.  I can deal with that.  In fact, I tihnk I may drop the default
limit to 20 characters, then, as a workaround is available for those
who wish to use it.

Cheers,

Derek
- --
                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBQcm8LD1OTBfyMaQRAjVDAKC7oK/ChhnoENM2pqYrbd4pk0y2nQCfb8I/
Kf4CQuGd7zR4W6eeweh0aZk=
=NWcD
-----END PGP SIGNATURE-----





reply via email to

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