Re: GNU GRUB maintenance

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Fri, Oct 09, 2015 at 08:30:01PM -0400, Konrad Rzeszutek Wilk wrote:
> On October 9, 2015 8:14:39 AM EDT, "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com> wrote:
> >On 08.10.2015 21:34, Konrad Rzeszutek Wilk wrote:
> >> On October 8, 2015 10:52:25 AM EDT, Andrei Borzenkov
> ><arvidjaar@gmail.com> wrote:
> >>> On Thu, Oct 8, 2015 at 12:14 AM, Vladimir 'φ-coder/phcoder'
> >Serbinenko
> >>> <phcoder@gmail.com> 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 = 8 hours, and there are 10 weeks left), then I would
concentrate on the existing patches + review.