From: Tilman Schmidt <tilman@imap.cc>
To: David Miller <davem@davemloft.net>
Cc: isdn@linux-pingi.de, hjlipp@web.de, keil@b1-systems.de,
i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] ISDN patches for net-next
Date: Tue, 22 Jan 2013 09:23:46 +0100 [thread overview]
Message-ID: <50FE4C92.3060103@imap.cc> (raw)
In-Reply-To: <20130121.173810.2229077237480842007.davem@davemloft.net>
Am 21.01.2013 23:38, schrieb David Miller:
> Patches 1-5 applied to net-next, patch 6 applied to 'net' and queued
> up for -stable.
Thanks.
> We don't have changes bypass 'net' and go into stable from net-next
> like you intended. We also don't use CC: stable for networking
> patches, you ask me to queue them up into my -stable patch queue
> for networking instead.
I see. Is there somewhere I can read up on the workflow for networking
patches and how it fits in with the general plan of things?
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
prev parent reply other threads:[~2013-01-22 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 21:57 [PATCH 0/6] ISDN patches for net-next Tilman Schmidt
2013-01-21 21:57 ` [PATCH 3/6] isdn/gigaset: beautify interface.c Tilman Schmidt
2013-01-21 21:57 ` [PATCH 1/6] isdn/divert: fix readability damage Tilman Schmidt
2013-01-21 21:57 ` [PATCH 2/6] isdn/gigaset: leave DLE mode before hanging up Tilman Schmidt
2013-01-21 21:57 ` [PATCH 6/6] isdn/gigaset: fix zero size border case in debug dump Tilman Schmidt
2013-01-21 21:57 ` [PATCH 4/6] isdn/gigaset: beautify common.c Tilman Schmidt
2013-01-21 21:57 ` [PATCH 5/6] isdn/gigaset: beautify ev-layer.c Tilman Schmidt
2013-01-21 22:38 ` [PATCH 0/6] ISDN patches for net-next David Miller
2013-01-22 8:23 ` Tilman Schmidt [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=50FE4C92.3060103@imap.cc \
--to=tilman@imap.cc \
--cc=davem@davemloft.net \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=keil@b1-systems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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).