From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qg0-x234.google.com ([2607:f8b0:400d:c04::234]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aG1wo-0007lI-Vi for barebox@lists.infradead.org; Mon, 04 Jan 2016 10:01:08 +0000 Received: by mail-qg0-x234.google.com with SMTP id o11so250402320qge.2 for ; Mon, 04 Jan 2016 02:00:44 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20160104085913.GD13058@pengutronix.de> References: <20160104085913.GD13058@pengutronix.de> From: Yegor Yefremov Date: Mon, 4 Jan 2016 11:00:24 +0100 Message-ID: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Patchwork for Barebox To: Sascha Hauer Cc: barebox@lists.infradead.org On Mon, Jan 4, 2016 at 9:59 AM, Sascha Hauer wrote: > Hi Yegor, > > On Tue, Dec 29, 2015 at 08:14:26AM +0100, Yegor Yefremov wrote: >> Hi Sascha, >> >> are you going to add Barebox to https://patchwork.ozlabs.org/? I'm >> using this service with Buildroot and it really provides a good patch >> overview. > > Would I have to actively use it or is it still useful if it only > collects patches and nobody updates the status to superseeded, applied, > and others? In Buildroot the maintainers update patch status, when it was upstreamed, rejected or needs rework. The submitters should at least mark their patches as "superseded", if they send a new version. So both parties are using it actively. Yegor _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox