From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 1/3] TIPC: Removing EXPERIMENTAL label Date: Fri, 25 May 2012 16:24:45 -0400 (EDT) Message-ID: <20120525.162445.1446193191065858422.davem@davemloft.net> References: <20120524195816.GA6487@windriver.com> <20120524.161231.1058511318935925082.davem@davemloft.net> <20120525190506.GB25102@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: jon.maloy@ericsson.com, netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net, allan.stephens@windriver.com, maloy@donjonn.com To: paul.gortmaker@windriver.com Return-path: In-Reply-To: <20120525190506.GB25102@windriver.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tipc-discussion-bounces@lists.sourceforge.net List-Id: netdev.vger.kernel.org From: Paul Gortmaker Date: Fri, 25 May 2012 15:05:06 -0400 > OK, what I'm hearing is that you'd prefer I continue to collect up TIPC > patches and issue pull requests for a while longer. I can do that. Any > specifics of how you'd like things done? -- e.g. if the reviews of new > TIPC development patches takes place here on netdev before I stage them, > will that create extra work for you dealing with them in patchworks? When you want the TIPC patches reviewed here you can simply post the set, and since you're informing me how this will work I'll know that you'll send me a pull request later, and therefore I can mark the patches as "Awaiting Upstream" or similar in patchwork. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/