Russ Tremain [EMAIL PROTECTED] writes:
Yep, it will break my code if you have a filename:
foo,2.3 1.3,bar
So far, no one has been this perverted... :)
Sounds like you are familiar with this problem.
just wanted to consider what level of perversion the hack would
withstand. in
Sent: Friday, May 11, 2001 8:02 AM
To: Russ Tremain
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: cvs patches notes
Russ Tremain [EMAIL PROTECTED] writes:
Yep, it will break my code if you have a filename:
foo,2.3 1.3,bar
So far, no one has been
Cheers,
-Russ
([EMAIL PROTECTED])
from: http://www.mail-archive.com/bug-cvs@gnu.org/msg00975.html
From: Rob Saccoccio
Subject: cvs patches notes
Date: Fri, 13 Apr 2001 10:03:52 -0700
I've identified and fixed (or worked around) some issues with cvs and
thought I'd pass 'em along
Russ Tremain [EMAIL PROTECTED] writes:
Hi Rob -
In regards to your logmsg.c patch, I have been able
to kludge around the white space problem by use
%{vsV} in the format specifier, and then joining
the arguments passed by the shell back together
in my loginfo script. I can then recognize
it with
your {t} specifier code. May be a couple
of days before I get to it, tho...
Cheers,
-Russ
([EMAIL PROTECTED])
from: http://www.mail-archive.com/bug-cvs@gnu.org/msg00975.html
From: Rob Saccoccio
Subject: cvs patches notes
Date: Fri, 13 Apr 2001 10:03:52 -0700
I've identified and fixed
I've identified and fixed (or worked around) some issues with cvs and
thought I'd pass 'em along...
1. There's a "bogus kludge" in server.c wrapped by "#ifdef sun" that applies
to pretty old unpatched versions of SunOS. Maybe an autoconf script could
be written to test for the condition that
