Jan Beulich writes ("Re: Pygrub backports"):
> On 27.02.15 at 15:41, wrote:
> > So if you don't mind too much, can we have them in 4.4.2 ? In which
> > case I would push them right away.
>
> Sure, go ahead.
Thanks. They were already in 4.5. I have backported them all to 4.3
and 4.4. There wa
>>> On 27.02.15 at 15:41, wrote:
> Jan Beulich writes ("Re: Pygrub backports"):
>> >>> On 27.02.15 at 13:29, wrote:
>> > I think the following commits from master should be considered for
>> > backport:
>>
>> Looks reasonable. Question is - do you still want this for 4.4.2 or
>> only afterwards?
Ian Campbell writes ("Re: Pygrub backports"):
> Sounds good. If we could also get an example of the problematic grub.cfg
> to be checked into xen.git/tools/pygrub/examples that would be handy
> too.
I have asked the reporter for a (suitably-laundered) copy and some
info about how it was generated.
Jan Beulich writes ("Re: Pygrub backports"):
> >>> On 27.02.15 at 13:29, wrote:
> > I think the following commits from master should be considered for
> > backport:
>
> Looks reasonable. Question is - do you still want this for 4.4.2 or
> only afterwards? If for it, then can these please go in be
>>> On 27.02.15 at 13:29, wrote:
> I think the following commits from master should be considered for
> backport:
Looks reasonable. Question is - do you still want this for 4.4.2 or
only afterwards? If for it, then can these please go in before RC2
(which really is only pending a push on the bran
On Fri, 2015-02-27 at 12:29 +, Ian Jackson wrote:
> I think the following commits from master should be considered for
> backport:
>
> 0c12e5b7427b4dfd2dfabf21f6b0e6e24bc8e864
> tools/pygrub: Fix extlinux when /boot is a separate partition from /
>
> d1b93ea2615bd789ee28901f1f1c05ffb319cb61
>
