On a related note, any objections against checking in the debian/
support tree into the master CVS?
Please go ahead; the added visibility of what happens there is a good
thing, so everybody who knows Pike can help suggest what might be good
and bad ways of following Debian's guidelines and the
On Sun, Mar 09, 2008 at 12:13:37PM +0100, Stephen R. van den Berg wrote:
On a related note, any objections against checking in the debian/
support tree into the master CVS?
it already exists in packaging/debian/
greetings,martin.
--
cooperative communication with sTeam - caudium,
On Sat, 8 Mar 2008, Arne Goedeke wrote:
Also with this particular case (when the first constant is wrong), pike
segfaults, apparently in f_function_name called by _sprintf in the last
backtrace frame of that
compile error.
I looked into it again and the problem seems to be that in
On Sat, 8 Mar 2008, Arne Goedeke wrote:
Also with this particular case (when the first constant is wrong), pike
segfaults, apparently in f_function_name called by _sprintf in the last
backtrace frame of that
compile error.
I looked into it again and the problem seems to be that in
