From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
Marko Kohtala <marko.kohtala@gmail.com>,
linux-parport@lists.infradead.org
Subject: Re: [patch 00/10] parport: ieee1284 fixes and cleanups
Date: Wed, 7 Sep 2005 22:07:33 -0500 [thread overview]
Message-ID: <200509072207.33725.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050907045052.508a0b4f.akpm@osdl.org>
On Wednesday 07 September 2005 06:50, Andrew Morton wrote:
> Marko Kohtala <marko.kohtala@gmail.com> wrote:
> >
> > > You just sent ten patches, all with the same name. This causes me grief
> > > (See http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, section 2a).
> >
> > I used "quilt mail" to send those patches and it seems it requires
> > some additional trick I did not notice to make the patches have
> > different subjects.
>
> I complained to the quilt guys about that and they did make a move to fix
> it, but I recall not being very happy with the proposal. Anyway, make sure
> you have the latest version and check the documentation - it's in there
> somewhere.
>
> As a last resort, put the title into the first line of the changelog and
> I'll cut-n-paste it.
>
I have the following in my .quiltrc
quilt_mail_patch_filter() {
local x=$(cat)
echo "$x" \
| sed -n \
-e 's/^\(To\|Cc\):/Recipient-\1:/ip' \
-e 's/^Subject:/Replace-Subject:/p' \
-e '/^\*\*\*\|---/q'
echo
# Discard the patch header, and pass on the rest
echo "$x" | awk '
!seen_from && (/^From: /) { print $0 "\n" ; seen_from = 1 }
!in_body && (/^[-A-Za-z]+:/) { next }
!in_body && (/^$/) { in_body = 1 ; next }
{ print }
'
}
And I have my patches in the following form:
Subject: mail subject
From: <someone if not I, git uses it>
<area (Usually Input)>: Short patch description
Decsription
Signed-off-by: X XX
---
<patch>
Then quilt mail command seems to do the right thing.
--
Dmitry
prev parent reply other threads:[~2005-09-08 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 18:31 [patch 00/10] parport: ieee1284 fixes and cleanups marko.kohtala
2005-09-05 18:31 ` [patch 01/10] " marko.kohtala
2005-09-05 18:31 ` [patch 02/10] " marko.kohtala
2005-09-05 18:31 ` [patch 03/10] " marko.kohtala
2005-09-05 18:31 ` [patch 04/10] " marko.kohtala
2005-09-05 18:31 ` [patch 05/10] " marko.kohtala
2005-09-05 18:31 ` [patch 06/10] " marko.kohtala
2005-09-05 18:31 ` [patch 07/10] " marko.kohtala
2005-09-05 18:31 ` [patch 08/10] " marko.kohtala
2005-09-05 18:31 ` [patch 09/10] " marko.kohtala
2005-09-05 18:31 ` [patch 10/10] " marko.kohtala
2005-09-07 9:31 ` [patch 00/10] " Andrew Morton
2005-09-07 11:34 ` Marko Kohtala
2005-09-07 11:50 ` Andrew Morton
2005-09-08 3:07 ` Dmitry Torokhov [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=200509072207.33725.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=marko.kohtala@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.