From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: alex.bennee@transitive.com
Cc: git@vger.kernel.org
Subject: Re: git-cvsexportcommit getting out of sync with CVS status requests
Date: Wed, 15 Aug 2007 17:53:50 +0200 [thread overview]
Message-ID: <46C3218E.6020309@fs.ei.tum.de> (raw)
In-Reply-To: <1187182726.13096.50.camel@murta.transitives.com>
Alex Bennee wrote:
> It looks like running a single CVS query for each file is the only
> solution.
I think internally CVS is doing single queries anyways. At least that was my impression.
Or we find out which order cvs is reporting the status. Maybe a simple sort of the pathnames could be sufficient?
cheers
simon
next prev parent reply other threads:[~2007-08-15 15:54 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
2007-08-15 15:53 ` Simon 'corecode' Schubert [this message]
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=46C3218E.6020309@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=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).