Re: git am and mangled subject lines

Hi, Phillip Susi wrote: > On 2/24/2014 3:19 PM, Junio C Hamano wrote: >> Phillip Susi writes: >>> git am already ignores the "[PATCH X/Y]" prefix that >>> format-patch adds. Is it possible to get it to ignore any >>> additional prefix that a bug tracker mangles into the subject >>> line? i.e.

Re: git am and mangled subject lines

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/24/2014 3:19 PM, Junio C Hamano wrote: > Phillip Susi writes: > >> git am already ignores the "[PATCH X/Y]" prefix that >> format-patch adds. Is it possible to get it to ignore any >> additional prefix that a bug tracker mangles into the subjec

Re: git am and mangled subject lines

Phillip Susi writes: > git am already ignores the "[PATCH X/Y]" prefix that format-patch > adds. Is it possible to get it to ignore any additional prefix that a > bug tracker mangles into the subject line? i.e. "bug #:"? I think applypatch-msg hook is your friend in a case like this. -- T

Re: git am and mangled subject lines

Hi Phillip, Phillip Susi wrote: > git am already ignores the "[PATCH X/Y]" prefix that format-patch > adds. Is it possible to get it to ignore any additional prefix that a > bug tracker mangles into the subject line? i.e. "bug #:"? builtin/mailinfo.c is the place to start (see git-mailinfo

git am and mangled subject lines

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 git am already ignores the "[PATCH X/Y]" prefix that format-patch adds. Is it possible to get it to ignore any additional prefix that a bug tracker mangles into the subject line? i.e. "bug #:"? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.1