Re: commit output

[Derek Robert Price]

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

Mark D. Baushke wrote:

> >Yes, many messages are generated on the server and no, actual
> >"clients" attempting to parse the output of the server should not have
> >problems with the changes since the CVS client/server protocol is
> >rather sharply defined in such a way that merely altering some of the
> >messages destined for user consumption should not alter the client
> >interpretation.
>
> I know that some of the additions of "`" and "'" or otherwise altering
> what punctuation were around which files was what caused eclipse.org
> stuff to be broken for a while. It was this kind of change to the output
> of stable that I was trying to protect against if possible.


Hrm.  Interesting.  I was told at some point that they had their own
client.  Anyhow, it really does make sense to leave output alone on
feature, I guess.  Time to bump the feature -> stable date.  What did
you suggest, Mark?  6 months?  That's November...  Seems like a long
time...  :)

> >If some expect script is parsing the text messages _coming out of the
> >client_, it is possible that these changes could confuse that script.
>
>
> Sure, for example, there is the need to hack the sanity.sh regression
> tests...


Well, yes, but that gets committed with these sorts of changes, in
general.  :)

Derek
- --
                *8^)

Email: derek@ximbiot.com

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

iD8DBQFAoMzlLD1OTBfyMaQRApSAAKC5TpPLAVHz4mZbZN2733Px14TPdACePkRQ
B8EFSS07xWznPP/ATF/Ims4=
=4bNd
-----END PGP SIGNATURE-----