On 5/26/06, Cameron McBride <cameron.mcbride@xxxxxxxxx> wrote:
sorry, my bad. This error was discovered using the git stable, v1.3.3. Grabbing the latest at git://git.kernel.org/pub/scm/git/git.git showed the same problem.
Ok. You might want to retain that latest, it has some further fixes ;-)
> If that doesn't fix it, can you post the logs? I think you have to > declare CVS_LOG=/tmp/cvslog or somesuch. I'm assuming you mean the log from git-cvsserver (set via git/config with logfile=...)
I was actually thinking of setting the environment at the client end: CVS_CLIENT_LOG, http://cvsbook.red-bean.com/cvsbook.html#$CVS_CLIENT_LOG but it looks like you've got it mostly sorted.
Besides the log cutoff in the broken attempt, it appears the culprit is a lack of arguments being passed down as that is the only difference in the logs.
Yes, I was guessing as much. I am still curious about what parameters (and in what order) cvs 1.11.7 sends...
To quiet it down and get it to run - a crude hack seemed to work
It looks reasonable as a means to shut it up, but perhaps if we can figure out what the client is telling us... ;-) martin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html