From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zkita-0000BG-BW for mharc-grub-devel@gnu.org; Fri, 09 Oct 2015 21:24:22 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkitX-0000AI-7E for grub-devel@gnu.org; Fri, 09 Oct 2015 21:24:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkitT-0003lj-2J for grub-devel@gnu.org; Fri, 09 Oct 2015 21:24:19 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:26534) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkitS-0003kt-PV for grub-devel@gnu.org; Fri, 09 Oct 2015 21:24:14 -0400 Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t9A1O98N014853 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Oct 2015 01:24:09 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.13.8/8.13.8) with ESMTP id t9A1O8bV016103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 10 Oct 2015 01:24:09 GMT Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id t9A1O8Ls009620; Sat, 10 Oct 2015 01:24:08 GMT Received: from konrad-lan.dumpdata.com (/209.6.196.81) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 09 Oct 2015 18:24:08 -0700 Date: Fri, 9 Oct 2015 21:24:04 -0400 From: Konrad Rzeszutek Wilk To: The development of GNU GRUB , "Vladimir =?utf-8?Q?'=CF=86-coder=2Fphcoder'?= Serbinenko" , Andrei Borzenkov Subject: Re: GNU GRUB maintenance Message-ID: <20151010012403.GA9965@konrad-lan.dumpdata.com> References: <56158B2B.6040205@gmail.com> <0E11E6D6-2448-4F86-9720-63C115AD08FD@oracle.com> <5617AFAF.5020406@gmail.com> <614D254E-ADC8-46A3-A5C2-E534BD91B7A8@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <614D254E-ADC8-46A3-A5C2-E534BD91B7A8@oracle.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Source-IP: userv0022.oracle.com [156.151.31.74] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by userp1040.oracle.com id t9A1O98N014853 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Oct 2015 01:24:20 -0000 On Fri, Oct 09, 2015 at 08:30:01PM -0400, Konrad Rzeszutek Wilk wrote: > On October 9, 2015 8:14:39 AM EDT, "Vladimir '=CF=86-coder/phcoder' Ser= binenko" wrote: > >On 08.10.2015 21:34, Konrad Rzeszutek Wilk wrote: > >> On October 8, 2015 10:52:25 AM EDT, Andrei Borzenkov > > wrote: > >>> On Thu, Oct 8, 2015 at 12:14 AM, Vladimir '=CF=86-coder/phcoder' > >Serbinenko > >>> wrote: > >>>> Hello, all. I'm sorry for not being available to do enough > >>> maintenance > >>>> for GRUB in last time but I was overbooked. Yet there is a good > >news. > >>> At > >>>> Google there is a 20% project and GRUB has been approved as 20% > >>> project > >>>> for me. The goal is to have 2.02 released before the end of this > >>> year. > >>>> Other than the raw lack of time there is another issue which makes > >>>> maintenance difficult: inefficient VCS. > >>> > >>> VCS is actually OK. The project of size Linux kernel seems to work Looking at the grub2 mailing list there hasn't been a ton of patches. And even if there is a pickup of it - is it going to be around 1K a month or more like in 100s? If it is going to be in 100~ or so per month - I would think that the existing mechanism of: 1) save email in mbox file 2) at the end of day, 'git am -s' < mbox file. 3) git push Would work - it is a five minute job. (This is assuming that the patches don't break a build and so on - if they do, then you can break this up and complain to the folks that post patches that it does not build,etc). If you are thinking there is going to 1K or so then some automated system makes sense... but if you are trying to get a release out before the end of this year and only have 10 business days to do this (20% of 40 week =3D 8 hours, and there are 10 weeks left), then I would concentrate on the existing patches + review.