From: Yann Dirson <ydirson@altern.org>
To: Chris Shoemaker <c.shoemaker@cox.net>
Cc: GIT list <git@vger.kernel.org>, cvsps@dm.cobite.com
Subject: Re: [PATCH] CVSps fixed; git-cvsimport works, too
Date: Sat, 17 Jun 2006 20:51:27 +0200 [thread overview]
Message-ID: <20060617185126.GS7766@nowhere.earth> (raw)
In-Reply-To: <20060617143443.GA29602@pe.Belkin>
On Sat, Jun 17, 2006 at 10:34:43AM -0400, Chris Shoemaker wrote:
> Are you saying there was no pre-existing cache file when the patched
> version was first run?
It was the sample script you provided to demonstrate the problem which
showed the new issue: it does a "cvsps -x" first, then runs
git-cvsimport, which runs "cvsps -u". That one does fails. I'm
pretty sure the cache does not exist beforehand, since your script
creates the repo in a temporary directory.
BTW, I'll see about adding a testsuite to cvsps, based on the
framework used by git. All these scriptlets used to exhibit the
various problems have to be kept somewhere.
> Did you delete it? If so, then there's a bug somewhere.
I do think there is a bug somewhere :)
> The complaint is basically, Hey, there's an initial branch
> determination already made for this file, but it's not the one I would
> have made, so it must have been restored from a cache file that I
> didn't make.
OK, thanks for the clarification.
Best regards,
--
Yann Dirson <ydirson@altern.org> |
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
prev parent reply other threads:[~2006-06-17 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 12:21 [PATCH] CVSps fixed; git-cvsimport works, too Yann Dirson
2006-06-17 13:20 ` Chris Shoemaker
2006-06-17 13:47 ` Yann Dirson
2006-06-17 14:34 ` Chris Shoemaker
2006-06-17 18:51 ` Yann Dirson [this message]
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=20060617185126.GS7766@nowhere.earth \
--to=ydirson@altern.org \
--cc=c.shoemaker@cox.net \
--cc=cvsps@dm.cobite.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).