From: Junio C Hamano <gitster@pobox.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2] format-patch: introduce format.outputDirectory configuration
Date: Wed, 28 Oct 2015 10:59:43 -0700 [thread overview]
Message-ID: <xmqqziz2kh68.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqk2rj8kf5.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 21 Sep 2015 15:41:34 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Looks like there were mostly editorial niggles and no fundamental
> flaws in the design of the patch; it is somewhat a shame to make all
> the efforts go to waste. Will we be seeing an update soon?
Second ping as I am going through the what's cooking reports and
trying to decide which topics listed in [Stalled] state need to be
discarded from my tree.
Not that my dropping a topic from 'pu' means very much (a dropped
topic can still be submitted and requeued after all), even if you
are no longer interested on the topic, hearing from you would help
others who may be interested in helping the topic to completion.
Thanks.
next prev parent reply other threads:[~2015-10-28 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 18:28 [PATCH v2] format-patch: introduce format.outputDirectory configuration Alexander Kuleshov
2015-06-19 20:34 ` Eric Sunshine
2015-09-21 22:41 ` Junio C Hamano
2015-09-22 0:05 ` Eric Sunshine
2015-10-28 17:59 ` Junio C Hamano [this message]
2016-01-10 2:30 ` [PATCH v3] " Stephen P. Smith
2016-01-10 3:47 ` Eric Sunshine
2016-01-11 0:30 ` [PATCH v4] " Stephen P. Smith
2016-01-11 3:55 ` Eric Sunshine
2016-01-11 4:00 ` Eric Sunshine
2016-01-13 4:48 ` [PATCH v5] " Stephen P. Smith
2016-01-13 6:52 ` Eric Sunshine
2016-01-13 13:20 ` [PATCH v6] " Stephen P. Smith
2016-01-13 18:27 ` Eric Sunshine
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=xmqqziz2kh68.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kuleshovmail@gmail.com \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.