From: Junio C Hamano <gitster@pobox.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: git@vger.kernel.org
Subject: Re: notice: pu broken tonight
Date: Wed, 10 Jun 2009 00:56:07 -0700 [thread overview]
Message-ID: <7vzlcgr088.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20090610074400.GA26020@pengutronix.de> ("Uwe Kleine-König"'s message of "Wed\, 10 Jun 2009 09\:44\:00 +0200")
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
> Hello Junio,
>
> On Tue, Jun 09, 2009 at 01:36:20AM -0700, Junio C Hamano wrote:
>> Other than that I
>> do not think I forgot to queue any patch I saw on the list.
> What about
>
> http://news.gmane.org/find-root.php?group=gmane.comp.version-control.git&article=120990
> ? I think it's save, but I didn't get any feed-back by you yet.
Nor anybody else for that matter ;-).
A patch that adds a new feature to a low-level building block without any
in-tree users, especially if there is no test for it, ranks very low in
the priority scale when I am short of time.
next prev parent reply other threads:[~2009-06-10 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 8:36 notice: pu broken tonight Junio C Hamano
2009-06-09 17:11 ` René Scharfe
2009-06-10 7:44 ` Uwe Kleine-König
2009-06-10 7:56 ` Junio C Hamano [this message]
2009-06-10 9:42 ` [PATCH 1/2] more tests for git rev-parse --parse-opt Uwe Kleine-König
2009-06-10 9:42 ` [PATCH 2/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Uwe Kleine-König
2009-06-10 10:37 ` [PATCH 1/2] more tests for git rev-parse --parse-opt Johannes Sixt
2009-06-10 14:16 ` Uwe Kleine-König
2009-06-13 23:58 ` Uwe Kleine-König
2009-06-13 23:58 ` [PATCH 2/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Uwe Kleine-König
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vzlcgr088.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).