git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Cameron McBride" <cameron.mcbride@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-cvsserver wart?
Date: Fri, 26 May 2006 15:23:22 +1200	[thread overview]
Message-ID: <46a038f90605252023v5ff3fd65l9a991b3bbfa0a024@mail.gmail.com> (raw)
In-Reply-To: <dcedf5e20605252011v6738dc9dg3d4801144d3e9898@mail.gmail.com>

On 5/26/06, Cameron McBride <cameron.mcbride@gmail.com> 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

  reply	other threads:[~2006-05-26  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 16:42 git-cvsserver wart? Cameron McBride
2006-05-25 21:19 ` Martin Langhoff
2006-05-26  3:11   ` Cameron McBride
2006-05-26  3:23     ` Martin Langhoff [this message]
2006-05-26  3:57       ` Cameron McBride
2006-05-26  3:24     ` Cameron McBride
2006-05-26  3:28       ` Martin Langhoff
2006-05-26  3:34         ` Cameron McBride

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46a038f90605252023v5ff3fd65l9a991b3bbfa0a024@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=cameron.mcbride@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).