From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tilman Schmidt <tilman@imap.cc>
Subject: Re: [PATCH 0/6] ISDN patches for net-next
Date: Tue, 22 Jan 2013 09:23:46 +0100
Message-ID: <50FE4C92.3060103@imap.cc>
References: <20130121-patch-isdn-00.tilman@imap.cc> <20130121.173810.2229077237480842007.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
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
To: David Miller <davem@davemloft.net>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20130121.173810.2229077237480842007.davem@davemloft.net>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

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

--=20
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge=F6ffnet mindestens haltbar bis: (siehe R=FCckseite)