Re: inetd question related to cvs (not usual pserver doesn't workFAQ)
[EMAIL PROTECTED] wrote: An easier way to look at the pserver client/server dialog is to define the CVS_CLIENT_LOG environment variable with the base file name for the log on the client. Yes; thanks. What I'm actually trying to do is harvest some information from the pserver connection that should be exposed to commitinfo and the like (like the -r option to commit--if someone commits a file and says -r 2.4, there's no way to get that 2.4 inside a commitinfo script). If there's a way to get these kinds of things with stock cvs, I'd like to do that. Anyhow, I thought I could sniff a bit of extra information via a server side wrapper and then pass it on (in the environment, perhaps) so my commitinfo scripts could make use of it. Guess I can't really do that. Cheers, Laird
Re: inetd question related to cvs (not usual pserver doesn't workFAQ)
"Laird" == Laird Nelson [EMAIL PROTECTED] writes: Laird [EMAIL PROTECTED] wrote: An easier way to look at the pserver client/server dialog is to define the CVS_CLIENT_LOG environment variable with the base file name for the log on the client. Laird Yes; thanks. What I'm actually trying to do is harvest some information Laird from the pserver connection that should be exposed to commitinfo and the Laird like (like the -r option to commit--if someone commits a file and says Laird -r 2.4, there's no way to get that 2.4 inside a commitinfo script). If Laird there's a way to get these kinds of things with stock cvs, I'd like to Laird do that. Laird Anyhow, I thought I could sniff a bit of extra information via a server Laird side wrapper and then pass it on (in the environment, perhaps) so my Laird commitinfo scripts could make use of it. Guess I can't really do that. A while ago there was a patch (against 1.10.7) by John Cavanaugh which made cvs provide extended information to commitinfo scripts (AlternateInfo). Maybe you might want to check this out (I messed it up - I can't find it anymore). Joerg
