git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Christian Biesinger <cbiesinger@web.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Ignore commits for which cvsps can't identify a branch
Date: Fri, 10 Feb 2006 15:25:09 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602101517290.19172@g5.osdl.org> (raw)
In-Reply-To: <43ED0D63.5090105@web.de>



On Fri, 10 Feb 2006, Christian Biesinger wrote:
> 
> I have to admit that I can't actually tell you for sure, since I still get a
> failure later (I think it's because cvsps orders changesets wrongly).

Do you have a recent version of "cvsps"? The wrong ordering happened quite 
often with old cvsps versions. So make sure you absolutely have 2.1.

Also, David Mansfield may not be maintaining it horribly actively, but 
that's probably because it's purely a "minimal maintenance" project for 
him by now. He reacted in a very timely manner when we pointed out 
specific bugs, so if you can pinpoint the exact thing cvsps does wrong, I 
bet David will be more than happy to apply patches or perhaps even fix it 
himself and make a new version.

So while it's fine to work around cvsps problems inside "git cvsimport", 
it's even better if you could try to see if you can figure out why they 
happen in the first place. The source code wasn't all that unreadable from 
what I can remember.

		Linus

  reply	other threads:[~2006-02-10 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 21:02 [PATCH] Ignore commits for which cvsps can't identify a branch Christian Biesinger
2006-02-10 21:21 ` Junio C Hamano
2006-02-10 22:02   ` Christian Biesinger
2006-02-10 23:25     ` Linus Torvalds [this message]
2006-06-10 19:24 ` Yann Dirson
2006-06-10 19:45   ` Christian Biesinger

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=Pine.LNX.4.64.0602101517290.19172@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=cbiesinger@web.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).