From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Pierre Habouzit <madcoder@debian.org>, git@vger.kernel.org
Subject: Re: [PATCH v3] parse-opt: migrate builtin-ls-files.
Date: Sat, 14 Feb 2009 12:04:44 -0800 [thread overview]
Message-ID: <7vmycoss2r.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090214121631.GG4371@genesis.frugalware.org> (Miklos Vajna's message of "Sat, 14 Feb 2009 13:16:31 +0100")
Miklos Vajna <vmiklos@frugalware.org> writes:
> On Wed, Jan 14, 2009 at 07:16:38PM -0800, Junio C Hamano <gitster@pobox.com> wrote:
>> Miklos Vajna <vmiklos@frugalware.org> writes:
>>
>> > Was this dropped on the floor by accident?
>>
>> I am not fundamentally opposed to the parseopt conversion, but I was
>> somewhat discouraged from taking another one, after we got burned by the
>> one that converted git-apply without much visible gain but with a new bug.
>>
>> Because ls-files is a plumbing, it has somewhat lower priority for user
>> friendliness than any other patches currently in-flight on the list; hence
>> it has been backburnered. It still is kept in my Inbox.
>
> I'm just asking again as I see the parseopt patch for builtin-config now
> on the list.
>
> Should I just resend this patch after v1.6.2?
You can do it either way, and a resend after v1.6.2 is certainly
appreciated,
As I said earlier in "What's cooking", 'pu' and 'next' are open during
this freeze cycle as an experiment.
I limit my bandwidth for handing anything non-fix during the rc freeze
period as always. The only difference from previous cycles is that the
cap used to be set to near-absolute-zero, but in this cycle it is not.
It still is capped and updates to 'pu' and 'next' are "as time permits"
basis.
next prev parent reply other threads:[~2009-02-14 20:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 0:11 [PATCH] parse-opt: migrate builtin-ls-files Miklos Vajna
2009-01-06 10:22 ` Pierre Habouzit
2009-01-07 3:11 ` [PATCH v2] " Miklos Vajna
2009-01-07 14:46 ` Pierre Habouzit
2009-01-08 0:55 ` [PATCH v3] " Miklos Vajna
2009-01-08 1:10 ` Johannes Schindelin
2009-01-08 1:54 ` Miklos Vajna
2009-01-15 0:14 ` Miklos Vajna
2009-01-15 3:16 ` Junio C Hamano
2009-01-15 3:48 ` Miklos Vajna
2009-02-14 12:16 ` Miklos Vajna
2009-02-14 20:04 ` Junio C Hamano [this message]
2009-02-14 20:56 ` Johannes Schindelin
2009-02-15 19:54 ` [PATCH] " Miklos Vajna
2009-02-15 20:13 ` Johannes Schindelin
2009-02-15 22:07 ` Miklos Vajna
2009-02-16 12:20 ` [PATCH] Turn the flags in struct dir_struct into a single variable Johannes Schindelin
2009-02-16 21:47 ` Miklos Vajna
2009-02-17 14:27 ` [PATCH] parse-opt: migrate builtin-ls-files Miklos Vajna
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=7vmycoss2r.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=vmiklos@frugalware.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 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).