On 10/03/2016 05:59 PM, William Hubbs wrote:
>
> - The only real problem with grub:2 has to do with pperception. Yes,
> their documentation has a strong preference toward using their
> configuration script (grub-mkconfig) to generate your grub.cfg, but
> this is not required.
>
Migration
On Mon, Oct 3, 2016, at 16:59 CDT, William Hubbs wrote:
> All,
>
> I want to look into removing grub:0 from the tree; here are my thoughts
> on why it should go.
>
> - the handbook doesn't document grub:0; we officially only support
> grub:2.
>
> - Removing grub:0 from the tree doesn't stop y
All,
I want to look into removing grub:0 from the tree; here are my thoughts
on why it should go.
- the handbook doesn't document grub:0; we officially only support
grub:2.
- There are multiple bugs open against grub:0 (15 at my last count). A
number of these as I understand it are because o
Our bug queue has 84 bugs!
If you have some spare time, please help assign/sort a few bugs.
To view the bug queue, click here: http://bit.ly/m8PQS5
Thanks!
On Sun, 2 Oct 2016 22:06:19 -0400
Ian Stakenvicius wrote:
> On 02/10/16 04:59 PM, James Le Cuirot wrote:
> > On Sun, 2 Oct 2016 21:48:04 +0100
> > James Le Cuirot wrote:
> >
> >> SRC_URI="gogdownloader://tomb_raider_1/en1installer1 ->
> >> setup_tomb_raider_${PV}.exe" IUSE="gogdownloader"
> >
On Mon, Oct 3, 2016 at 3:09 PM, Kent Fredric wrote:
> On Mon, 3 Oct 2016 14:37:15 +0800
> konsolebox wrote:
>
>> But anyway, what do you think about just enabling
>> IUSE="+system-readline" by default to any version, and just rely on
>> KEYWORDS="" to prevent the user from misusing it with a pre-
On Mon, 3 Oct 2016 14:37:15 +0800
konsolebox wrote:
> But anyway, what do you think about just enabling
> IUSE="+system-readline" by default to any version, and just rely on
> KEYWORDS="" to prevent the user from misusing it with a pre-release
> version of bash? I believe we can both agree on th
