From: Mike Ralphson <mike.ralphson@gmail.com>
To: Nick Woolley <nickwoolley@yahoo.co.uk>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-cvsexportcommit can't commit files which have been removed from CVS
Date: Wed, 10 Jun 2009 09:06:01 +0100 [thread overview]
Message-ID: <e2b179460906100106x2b9c0bb4r931b0a12959d4314@mail.gmail.com> (raw)
In-Reply-To: <4A1F1CF5.8030002@yahoo.co.uk>
2009/5/29 Nick Woolley <nickwoolley@yahoo.co.uk>
> Added a test to t9200-git-cvsexportcommit.sh, which tests that we can
> re-commit a removed filename which remains in CVS's attic. This adds a
> file 'attic_gremlin' in CVS, then "removes" it, then tries to commit a
> file with the same name from git.
Hi Nick, I'm seeing intermittent failures since your new test was
added to 'next' on AIX 5.3
cvs commit: Up-to-date check failed for ` space'
cvs [commit aborted]: correct above errors first!
* FAIL 15: re-commit a removed filename which remains in CVS attic
* failed 1 among 15 test(s)
Is there a possibility this test has a race condition?
Let me know if there's anything I can do to help debug it.
It could be a bug in the ancient CVS I have here (1.11.1p1) though.
cvs status: Examining .
===================================================================
File: space Status: Needs Patch
As it's a file from the previous tests being fingered, I've cc'd a
couple of likely lads.
Mike
next prev parent reply other threads:[~2009-06-10 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 23:23 [PATCH] git-cvsexportcommit can't commit files which have been removed from CVS Nick Woolley
2009-06-10 8:06 ` Mike Ralphson [this message]
2009-06-11 14:10 ` Nick Woolley
2009-06-11 15:45 ` Junio C Hamano
2009-06-11 15:49 ` Junio C Hamano
2009-06-11 17:04 ` Junio C Hamano
2009-06-12 6:59 ` Robin Rosenberg
2009-07-02 13:50 ` Mike Ralphson
2009-07-06 13:23 ` Nick Woolley
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=e2b179460906100106x2b9c0bb4r931b0a12959d4314@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nickwoolley@yahoo.co.uk \
--cc=peff@peff.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).