From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2014, #04; Tue, 26)
Date: Wed, 27 Aug 2014 12:28:19 -0400 [thread overview]
Message-ID: <20140827162819.GB1432@peff.net> (raw)
In-Reply-To: <xmqqfvgieyoo.fsf@gitster.dls.corp.google.com>
On Wed, Aug 27, 2014 at 08:31:51AM -0700, Junio C Hamano wrote:
> > - jk/send-pack-many-refspecs; this is in pu, but I didn't see it in
> > "what's cooking". I'm concerned that the "ulimit" test gave you
> > trouble and you punted on it. :)
>
> It was picked up after the day's edition of "What's cooking" was
> written, or something, I think.
Ah, sorry to nag, then.
> > - "fast-export --anonymize"; I noticed you didn't pick this up at all.
> > I agree it has yet to prove its worth, but I wonder if it is worth
> > shipping it (possibly labeled as experimental and not to be depended
> > on) to get it in the hands of users. The intended use is getting bug
> > reports from users, who are not always savvy enough to pick up (and
> > possibly rebase) a patch from the list. I dunno.
>
> I was waiting for the topic to calm down a bit, without knowing if
> there will or will not be a reroll with some low-hanging fruit
> enhancement based on the discussion, to avoid an "oops, need to
> replace the one I queued but haven't pushed out yet with the new
> reroll".
Makes sense. I think the v2 I sent[1] is OK, and as far as I was
planning to take it for now (there were some other possible enhancements
discussed, but I think those can happen in-tree if somebody feels like
working on it).
-Peff
[1] http://article.gmane.org/gmane.comp.version-control.git/255646
next prev parent reply other threads:[~2014-08-27 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 22:09 What's cooking in git.git (Aug 2014, #04; Tue, 26) Junio C Hamano
2014-08-27 8:13 ` Jeff King
2014-08-27 15:31 ` Junio C Hamano
2014-08-27 16:28 ` Jeff King [this message]
2014-08-27 16:38 ` Junio C Hamano
2014-08-27 16:42 ` Jeff King
2014-08-28 3:33 ` Yue Lin Ho
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=20140827162819.GB1432@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).