From: Sven Eckelmann <sven@narfation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org,
David Miller <davem@davemloft.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: fix skb->data assignment
Date: Tue, 19 Jun 2012 14:41:34 +0200 [thread overview]
Message-ID: <2112512.N0gHzzFGDc@bentobox> (raw)
In-Reply-To: <1340107811.6871.32.camel@deadeye.wl.decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Tuesday 19 June 2012 13:10:11 Ben Hutchings wrote:
> [...]
>
> There's not much sense in a 'cc' if you're sending a new message (the
> backport) specificaly to stable. Instead, use a subject like
> '[PATCH 3.x] original commit summary'. You do need to make clear that
> this is a backport and not just a request to cherry-pick the upstream
> commit.
>
> Also, you should wait and send it after the original goes upstream,
> because stable maintainers will usually want to either apply or reject
> immediately rather than storing things up. Greg's scripts will tell you
> when this happens, or at least when he next checks.
Thanks a lot.
Regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-19 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 7:20 [B.A.T.M.A.N.] [PATCH] batman-adv: fix skb->data assignment Antonio Quartulli
2012-06-19 7:41 ` David Miller
2012-06-19 8:07 ` Sven Eckelmann
2012-06-19 9:02 ` David Miller
2012-06-19 9:51 ` Sven Eckelmann
2012-06-19 12:10 ` Ben Hutchings
2012-06-19 12:41 ` Sven Eckelmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-19 7:23 Antonio Quartulli
2012-06-14 20:21 Antonio Quartulli
2012-06-15 11:45 ` Sven Eckelmann
2012-06-15 11:50 ` Antonio Quartulli
2012-06-15 19:09 ` Marek Lindner
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=2112512.N0gHzzFGDc@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=stable@vger.kernel.org \
/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.