From: Werner LEMBERG <wl@gnu•org>
To: casey@nrlssc•navy.mil
Cc: git@vger•kernel.org, keithp@keithp•com
Subject: Re: serious problem with `git format-patch' & `git am'
Date: Fri, 27 Feb 2009 10:16:49 +0100 (CET) [thread overview]
Message-ID: <20090227.101649.156177765.wl@gnu.org> (raw)
In-Reply-To: <6HVVE8kW9V0CsNfW21a_Tqpt2s-IrJbt2_qdAvQ8r1tetEhb6jr18g@cipher.nrlssc.navy.mil>
> I was not aware of this behavior, but it looks like the '-k' option
> for both format-patch and git-am is what you want to use. It will
> prevent mailinfo from munging the commit message.
Tried it already. It doesn't help.
Werner
prev parent reply other threads:[~2009-02-27 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 22:03 serious problem with `git format-patch' & `git am' Werner LEMBERG
2009-02-26 10:42 ` Johannes Schindelin
2009-02-26 18:00 ` Brandon Casey
2009-02-27 1:11 ` Jakub Narebski
2009-02-27 2:10 ` Junio C Hamano
2009-02-27 15:47 ` Brandon Casey
2009-02-27 17:53 ` Junio C Hamano
2009-02-27 9:16 ` Werner LEMBERG [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=20090227.101649.156177765.wl@gnu.org \
--to=wl@gnu$(echo .)org \
--cc=casey@nrlssc$(echo .)navy.mil \
--cc=git@vger$(echo .)kernel.org \
--cc=keithp@keithp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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