Re: commitlog

[Derek Robert Price]

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

Mark D. Baushke wrote:

|Brian Murphy <brian@murphy.dk> writes:
|
|>>I have not really thought thru the implications of such a change, but it
|>>would be useful to be able to handle all of the possible Unicode
|>>characters that some filesystems are starting to use in filenames under
|>>some operating systems.
|>>
|>I think this is a bit ambitious - try seeing what happens when you run
|>"cvs up"
|>in a directory with a filename containing carriage returns:
|>
|>from bash:
|>$ touch $'a\nb'
|>$ cvs up
|>? a
|>unrecognized request `b'
|>
|>Spaces on the other hand are reasonably easy to handle in that they
|>already work except for problems quoting when external programs are
|>called.
|
|
|Granted. However, choosing a solution that only addresses space
|characters in filenames when there would appear to be a more general
|problem to solve seems short-sighted. If we are going to move to a
|quoting mechanism, we should consider how to encode the various CVS/*
|book-keeping files as well to be able to represent such files as well
|as determine a way to get such files into command-line arguments.


I wrote a patch some time back to deal with some of this.  It is
attached to this issue:
<http://ccvs.cvshome.org/issues/show_bug.cgi?id=60>.  I've been waiting
on importing vasnprintf from GNULIB, which is waiting on error.c from
GNULIB, to commit it due to a dependancy on the otherwise unportable
snprintf.  I ported the patch forward to 1.12.1 fairly recently but I
tried to merge it forward to dev yesterday and got several conflicts.

There's a related issue about making use of some work CollabNet has
already done towards using XML as the transport mechanism here:
<http://ccvs.cvshome.org/issues/show_bug.cgi?id=25>.  If XML were used
it should be fairly easy to encode any XML supported charset in the data
stream.

Derek

- --
~                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
- --
Take my advice, I don't use it anyway.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/Qiu7LD1OTBfyMaQRArKaAKDuJ/QtjaymXhLLQQIUN+XmDzdThgCg0t1+
HCB92IAYRbEOK4Z+SfGJx4o=
=ADFt
-----END PGP SIGNATURE-----