From: Alex Bennee <alex.bennee@transitive.com>
To: git@vger.kernel.org
Subject: Re: git-cvsexportcommit getting out of sync with CVS status requests
Date: Wed, 15 Aug 2007 13:58:46 +0100 [thread overview]
Message-ID: <1187182726.13096.50.camel@murta.transitives.com> (raw)
In-Reply-To: <1187178510.13096.46.camel@murta.transitives.com>
On Wed, 2007-08-15 at 12:48 +0100, Alex Bennee wrote:
> Hi,
>
> Occasionally (usually when a lot of files have been added or moved in my
> git tree) git-cvsexportcommit gets confused when I'm exporting. I'll get
> the error like:
So I have figured out the reason it goes out of sync. CVS doesn't seem
to always report status in the order you give it on the command line
(which is rather crucial to the functioning of the script).
e.g. cvs status path/to/filea path/to/filev path/to/filec can return the
status in order
fileb
filea
filec
It looks like running a single CVS query for each file is the only
solution.
--
Alex Bennee - Alex.Bennee@transitive.com
Behind every great computer sits a skinny little geek.
next prev parent reply other threads:[~2007-08-15 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 11:48 git-cvsexportcommit getting out of sync with CVS status requests Alex Bennee
2007-08-15 12:58 ` Alex Bennee [this message]
2007-08-15 15:53 ` Simon 'corecode' Schubert
2007-08-15 16:11 ` Johannes Schindelin
2007-08-15 16:34 ` Simon 'corecode' Schubert
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=1187182726.13096.50.camel@murta.transitives.com \
--to=alex.bennee@transitive.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).