From: Adam Spiers <git@adamspiers.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git list <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] format-patch: --inline-single
Date: Fri, 22 Feb 2013 15:32:09 +0000 [thread overview]
Message-ID: <20130222153209.GF7860@pacific.linksys.moosehall> (raw)
In-Reply-To: <20130221231328.GA19808@sigill.intra.peff.net>
On Thu, Feb 21, 2013 at 06:13:28PM -0500, Jeff King wrote:
> On Thu, Feb 21, 2013 at 12:26:22PM -0800, Junio C Hamano wrote:
>
> > Some people may find it convenient to append a simple patch at the
> > bottom of a discussion e-mail separated by a "scissors" mark, ready
> > to be applied with "git am -c". Introduce "--inline-single" option
> > to format-patch to do so. A typical usage example might be to start
> > 'F'ollow-up to a discussion, write your message, conclude with "a
> > patch to do so may look like this.", and
> >
> > \C-u M-! git format-patch --inline-single -1 HEAD <ENTER>
> >
> > if you are an Emacs user. Users of other MUA's may want to consult
> > their manuals to find equivalent command to append output from an
> > external command to the message being composed.
>
> Interesting. I usually just do this by hand, but this could save a few
> keystrokes in my workflow.
Same here. This is great; thanks a lot both for working on it!
next prev parent reply other threads:[~2013-02-22 15:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 5:24 [BUG] git-check-ignore: Segmentation fault Zoltan Klinger
2013-02-19 13:40 ` Adam Spiers
2013-02-19 14:06 ` [PATCH 1/2] t0008: document test_expect_success_multi Adam Spiers
2013-02-19 14:06 ` [PATCH 2/2] check-ignore.c: fix segfault with '.' argument from repo root Adam Spiers
2013-02-19 17:54 ` Junio C Hamano
2013-02-19 19:07 ` Adam Spiers
2013-02-19 19:21 ` [PATCH v2 2/2] check-ignore.c, dir.c: " Adam Spiers
2013-02-19 19:59 ` Junio C Hamano
2013-02-19 22:03 ` Junio C Hamano
2013-02-20 1:57 ` Adam Spiers
2013-02-20 2:47 ` Junio C Hamano
2013-02-20 12:43 ` Adam Spiers
2013-02-20 1:30 ` Adam Spiers
2013-02-19 19:56 ` Re* [PATCH 2/2] check-ignore.c: " Junio C Hamano
2013-02-20 2:00 ` Adam Spiers
2013-02-20 2:53 ` Junio C Hamano
2013-02-20 10:47 ` Adam Spiers
2013-02-21 20:15 ` Junio C Hamano
2013-02-21 20:17 ` [PATCH 1/2] format-patch: rename "no_inline" field Junio C Hamano
2013-02-21 20:26 ` [PATCH 2/2] format-patch: --inline-single Junio C Hamano
2013-02-21 23:13 ` Jeff King
2013-02-21 23:41 ` Junio C Hamano
2013-02-21 23:47 ` Junio C Hamano
2013-02-22 15:32 ` Adam Spiers [this message]
2013-02-22 16:47 ` Junio C Hamano
2013-02-22 17:23 ` Jeff King
2013-02-19 17:37 ` [PATCH 1/2] t0008: document test_expect_success_multi Junio C Hamano
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=20130222153209.GF7860@pacific.linksys.moosehall \
--to=git@adamspiers.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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