From: Chris Packham <judge.packham@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Odd git am behavior rewriting subject, adding "ASoC: " prefix
Date: Wed, 5 Nov 2014 22:12:03 +1300 [thread overview]
Message-ID: <CAFOYHZAimkSMWC42S_C=OkNuz+cjT3vhsGo6AwuCtt8M2REkig@mail.gmail.com> (raw)
In-Reply-To: <1415149921.6634.1.camel@perches.com>
On Wed, Nov 5, 2014 at 2:12 PM, Joe Perches <joe@perches.com> wrote:
> I have a patch file created by git format-patch.
>
> Applying it via git am changes the subject prefix.
> Anyone know why?
>
> $ git --version
> git version 2.1.2
>
> $ git am -i 0002-staging-ft1000-Logging-message-neatening.patch
> Commit Body is:
> --------------------------
> staging: ft1000: Logging message neatening
>
> Use a more common logging style.
>
> o Convert DEBUG macros to pr_debug
> o Add pr_fmt
> o Remove embedded function names from pr_debug
> o Convert printks to pr_<level>
> o Coalesce formats and align arguments
> o Add missing terminating newlines
>
> Signed-off-by: Joe Perches <joe@perches.com>
> --------------------------
> Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all
>
> choosing "Y" emits:
>
> Applying: ASoC: staging: ft1000: Logging message neatening
>
> ASoC:? where does that come from?
>
>
Looks like you have an apply-patch-msg hook installed. What does the
output of 'ls -l .git/hooks' look like.
next prev parent reply other threads:[~2014-11-05 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 1:12 Odd git am behavior rewriting subject, adding "ASoC: " prefix Joe Perches
2014-11-05 9:12 ` Chris Packham [this message]
2014-11-05 13:51 ` Joe Perches
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='CAFOYHZAimkSMWC42S_C=OkNuz+cjT3vhsGo6AwuCtt8M2REkig@mail.gmail.com' \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=joe@perches.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).