From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: git@vger.kernel.org, 426617@bugs.debian.org
Subject: Re: git-cvsimport cannot handle zsh CVS repo
Date: Fri, 8 Jun 2007 07:19:14 +1200 [thread overview]
Message-ID: <46a038f90706071219h35d776d2m15a9dcf7f9bc24aa@mail.gmail.com> (raw)
In-Reply-To: <20070607073336.26979.qmail@178148a41cee98.315fe32.mid.smarden.org>
On 6/7/07, Gerrit Pape <pape@smarden.org> wrote:
> Hi, I'm stuck tracking down this issue, unfortunately reproducing it
> seems to take ages. Any help would be appreciated.
>
> Please see http://bugs.debian.org/426617
This is probably a problem with cvsps output on that repo. If you run
cvsps against the cvs repo, what does its output look like around/past
patchset 6965
There's a number of things that can confuse cvsps, as the cvs repo
format is horrid.
cheers,
martin
next prev parent reply other threads:[~2007-06-07 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 7:33 git-cvsimport cannot handle zsh CVS repo Gerrit Pape
2007-06-07 19:19 ` Martin Langhoff [this message]
2007-06-14 13:25 ` Gerrit Pape
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=46a038f90706071219h35d776d2m15a9dcf7f9bc24aa@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=426617@bugs.debian.org \
--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).