From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Steffen Prohaska" <prohaska@zib.de>
Cc: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.
Date: Thu, 10 May 2007 18:53:51 +1200 [thread overview]
Message-ID: <46a038f90705092353x107c738foa7db547ab29b1748@mail.gmail.com> (raw)
In-Reply-To: <380B28A3-5CD0-4371-A717-1D2629E6302D@zib.de>
On 5/10/07, Steffen Prohaska <prohaska@zib.de> wrote:
> I'll post a patch soon that takes the best of both: Call cvs status
> once with the list of touched files and parse the output. Only one
> connection is needed and only the minimal amount of status data is
> transferred.
Yes, please :-) I wrote cvsexportcommit originally, and use it on a
huge cvs checkout that is hosted on SF.net (slow!). My commits are
small (3~5 files). I agree with using only one connection so commits
with many files are sanity-checked faster, but status needs to ask
explicitly about the files it's about to touch.
cheers,
m
next prev parent reply other threads:[~2007-05-10 6:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 23:59 [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file Steffen Prohaska
2007-05-09 7:42 ` Steffen Prohaska
2007-05-09 7:45 ` [PATCH (corrected)] " Steffen Prohaska
2007-05-09 11:04 ` [PATCH] " Johannes Schindelin
2007-05-09 11:43 ` Steffen Prohaska
2007-05-09 12:25 ` Johannes Schindelin
2007-05-09 13:00 ` Steffen Prohaska
2007-05-09 20:30 ` Robin Rosenberg
2007-05-09 22:45 ` Steffen Prohaska
2007-05-09 23:06 ` [PATCH] Optimized cvsexportcommit: calling 'cvs status' once instead of once per touched file Steffen Prohaska
2007-05-10 6:53 ` Martin Langhoff [this message]
2007-05-10 7:08 ` [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file Junio C Hamano
2007-05-13 21:01 ` RFH for " Junio C Hamano
2007-05-13 21:51 ` Robin Rosenberg
2007-05-14 6:40 ` Martin Langhoff
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=46a038f90705092353x107c738foa7db547ab29b1748@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
--cc=robin.rosenberg.lists@dewire.com \
/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).