From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, "Steffen Prohaska" <prohaska@zib.de>,
"Martin Langhoff" <martin.langhoff@gmail.com>
Subject: Re: RFH for [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.
Date: Sun, 13 May 2007 23:51:24 +0200 [thread overview]
Message-ID: <200705132351.24867.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7vps54qvya.fsf_-_@assigned-by-dhcp.cox.net>
söndag 13 maj 2007 skrev Junio C Hamano:
> I'd like to have feedbacks on this patch, as I think what it
> tries to do is sensible and worth to have it in v1.5.2 if it
> works for people.
>
> Ack? Nack? YesButNeedsmorework?
Looks good, but I haven't tried it for production work yet.
-- robin
next prev parent reply other threads:[~2007-05-13 21:51 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 ` [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file Martin Langhoff
2007-05-10 7:08 ` Junio C Hamano
2007-05-13 21:01 ` RFH for " Junio C Hamano
2007-05-13 21:51 ` Robin Rosenberg [this message]
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=200705132351.24867.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=martin.langhoff@gmail.com \
--cc=prohaska@zib.de \
/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).