From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: alex.bennee@transitive.com, git@vger.kernel.org
Subject: Re: git-cvsexportcommit getting out of sync with CVS status requests
Date: Wed, 15 Aug 2007 18:34:56 +0200 [thread overview]
Message-ID: <46C32B30.8040504@fs.ei.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708151810000.19496@wbgn129.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
>> 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.
> Why then was cvsexportcommit so much slower without
> c56f0d9c661dc918a088e60d0ab69dd48019a9be?
Ah, my bad. Didn't use such a recent cvsexportcommit. So we need to mimic the cvs sorting.
cheers
simon
prev parent reply other threads:[~2007-08-15 16:35 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
2007-08-15 16:11 ` Johannes Schindelin
2007-08-15 16:34 ` Simon 'corecode' Schubert [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=46C32B30.8040504@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=Johannes.Schindelin@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.