From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse
Date: Wed, 29 Apr 2009 10:10:22 +0200 [thread overview]
Message-ID: <20090429081022.GA18521@pengutronix.de> (raw)
In-Reply-To: <20090429040804.GB14912@coredump.intra.peff.net>
Hi Jeff,
On Wed, Apr 29, 2009 at 12:08:04AM -0400, Jeff King wrote:
> On Tue, Apr 28, 2009 at 10:29:23PM +0200, Uwe Kleine-König wrote:
>
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > Documentation/git-rev-parse.txt | 5 +++++
> > builtin-rev-parse.c | 8 ++++++--
> > 2 files changed, 11 insertions(+), 2 deletions(-)
>
> I expected there to be a shell caller here or in patch 2/2, but there
> isn't. Is this for topgit?
Yes, I had topgit in mind when adding that option. Assuming it will
make it into git.git, I won't use it for some time though to not depend
on bleeding edge for topgit, though.
It wasn't intentionally that I sent the two patches in a series.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-04-29 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 20:29 [PATCH 1/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Uwe Kleine-König
2009-04-28 20:29 ` [PATCH 2/2] parseopt: fix documentation for --keep-dashdash Uwe Kleine-König
2009-04-29 4:08 ` [PATCH 1/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Jeff King
2009-04-29 8:10 ` Uwe Kleine-König [this message]
2009-06-07 18:19 ` [RESEND PATCH] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090429081022.GA18521@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).