From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nick Woolley <nickwoolley@yahoo.co.uk>,
Mike Ralphson <mike.ralphson@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [PATCH] git-cvsexportcommit can't commit files which have been removed from CVS
Date: Fri, 12 Jun 2009 08:59:32 +0200 [thread overview]
Message-ID: <200906120859.33139.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7vzlcehfbd.fsf@alter.siamese.dyndns.org>
torsdag 11 juni 2009 19:04:54 skrev Junio C Hamano <gitster@pobox.com>:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > Nick Woolley <nickwoolley@yahoo.co.uk> writes:
> >> Mike Ralphson wrote:
> >>> 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)
> > But it does seem to be repeatable; I wouldn't rule out a race condition.
>
> Ehh, sorry, it "does not" seem to be repeatable. Sometimes and only
> sometimes it fails...
CVS har a timestamp in CVS/Entries that has whole second resolution. In
addition it's built-in method for trying to work around the problem by sleeping
until the next second wraps around is flaky. cvsexportcommit already has
one sleep for this. Maybe it's not enough.
-- robin
next prev parent reply other threads:[~2009-06-12 6:59 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
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 [this message]
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=200906120859.33139.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike.ralphson@gmail.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).