From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Aug 2014, #04; Tue, 26)
Date: Wed, 27 Aug 2014 08:31:51 -0700 [thread overview]
Message-ID: <xmqqfvgieyoo.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140827081323.GA26538@peff.net> (Jeff King's message of "Wed, 27 Aug 2014 04:13:23 -0400")
Jeff King <peff@peff•net> writes:
> On Tue, Aug 26, 2014 at 03:09:34PM -0700, Junio C Hamano wrote:
>
>> --------------------------------------------------
>> [New Topics]
>
> There are a few misc topics of mine that I'd like to ping on:
>
> - jk/contrib-subtree-make-all; you picked up the topic, but it's not
> in pu or "what's cooking". Just forgotten, I think?
Correct, I think. Will requeue.
> - 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.
> - "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".
Thanks.
next prev parent reply other threads:[~2014-08-27 15:34 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 [this message]
2014-08-27 16:28 ` Jeff King
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=xmqqfvgieyoo.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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