* Odd git am behavior rewriting subject, adding "ASoC: " prefix
@ 2014-11-05 1:12 Joe Perches
2014-11-05 9:12 ` Chris Packham
0 siblings, 1 reply; 3+ messages in thread
From: Joe Perches @ 2014-11-05 1:12 UTC (permalink / raw)
To: git
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Odd git am behavior rewriting subject, adding "ASoC: " prefix
2014-11-05 1:12 Odd git am behavior rewriting subject, adding "ASoC: " prefix Joe Perches
@ 2014-11-05 9:12 ` Chris Packham
2014-11-05 13:51 ` Joe Perches
0 siblings, 1 reply; 3+ messages in thread
From: Chris Packham @ 2014-11-05 9:12 UTC (permalink / raw)
To: Joe Perches; +Cc: git
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Odd git am behavior rewriting subject, adding "ASoC: " prefix
2014-11-05 9:12 ` Chris Packham
@ 2014-11-05 13:51 ` Joe Perches
0 siblings, 0 replies; 3+ messages in thread
From: Joe Perches @ 2014-11-05 13:51 UTC (permalink / raw)
To: Chris Packham; +Cc: git
On Wed, 2014-11-05 at 22:12 +1300, Chris Packham wrote:
> 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.
[]
> > 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.
Correct. I didn't look there. Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-11-05 13:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-05 1:12 Odd git am behavior rewriting subject, adding "ASoC: " prefix Joe Perches
2014-11-05 9:12 ` Chris Packham
2014-11-05 13:51 ` Joe Perches
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).