git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Robert Anderson <rwa000@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] improve doc heading for git-bisect
Date: Sun, 8 Jun 2008 00:35:43 -0400	[thread overview]
Message-ID: <20080608043543.GB11194@sigill.intra.peff.net> (raw)
In-Reply-To: <9af502e50806070906u63e52de4wa0bc4dced0c4d984@mail.gmail.com>

On Sat, Jun 07, 2008 at 09:06:19AM -0700, Robert Anderson wrote:

> > FYI this line is not necessary, and should be removed from
> > git-format-patch output when pasting it to your MUA.
> 
> Err, then shouldn't it be removed from format-patch, rather than
> deleted manually every time format-patch is used?

As others have pointed out, the usual way for using format-patch is to
create an mbox that you then pull into your MUA (e.g., I do "git
format-patch --stdout origin >mbox; mutt -f mbox").

However, sometimes it is desirable to cut and paste, either because it
is inconvenient to bring the message into your MUA this way, or if you
are just putting a commit into an email you have already started
writing.

I was going to suggest a "--paste" option for format-patch which would
produce a nicer output for cutting and pasting, but it is trivial to do
with an alias:

  git config --global \
    alias.pastepatch \
    'format-patch --pretty=format:%s%n%n%b'

(actually, this loses the author information versus using the
--pretty=email format, but if you are just sending your own work, it is
fine).

It is essentially the same as "git log --stat -p" except that the commit
message is indented properly, and the revision arguments are interpreted
as format-patch does.

-Peff

  parent reply	other threads:[~2008-06-08  4:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07  7:06 [PATCH] improve doc heading for git-bisect Robert Anderson
2008-06-07  9:22 ` Jakub Narebski
2008-06-07 16:06   ` Robert Anderson
2008-06-07 16:25     ` Jakub Narebski
2008-06-07 17:47     ` Junio C Hamano
2008-06-08  4:35     ` Jeff King [this message]
2008-06-08 15:01       ` Johannes Schindelin
2008-06-08 21:27         ` Jeff King

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=20080608043543.GB11194@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=rwa000@gmail.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.
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).