From: "Kristian Høgsberg" <krh@redhat.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use a strbuf for copying the command line for the reflog.
Date: Tue, 04 Dec 2007 10:46:16 -0500 [thread overview]
Message-ID: <1196783176.2606.2.camel@hinata.boston.redhat.com> (raw)
In-Reply-To: <1196753147-20073-1-git-send-email-krh@redhat.com>
Doh, I forgot -n to git-format-patch again for this two patch series.
Maybe git-format-patch should default to -n when there's more than one
patch? Anyway, it should have been:
[PATCH 1/2] Use a strbuf for copying the command line for the reflog.
[PATCH 2/2] Rewrite builtin-fetch option parsing to use parse_options().
cheers,
Kristian
prev parent reply other threads:[~2007-12-04 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 7:25 [PATCH] Use a strbuf for copying the command line for the reflog Kristian Høgsberg
2007-12-04 7:25 ` [PATCH] Rewrite builtin-fetch option parsing to use parse_options() Kristian Høgsberg
2007-12-04 15:46 ` Kristian Høgsberg [this message]
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=1196783176.2606.2.camel@hinata.boston.redhat.com \
--to=krh@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).