public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: separate /usr preparation vote
Date: Tue, 27 Aug 2013 20:25:01 -0500	[thread overview]
Message-ID: <20130828012501.GA6295@linux1> (raw)
In-Reply-To: <521CFE65.3000509@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]

On Tue, Aug 27, 2013 at 03:30:45PM -0400, Rick "Zero_Chaos" Farina wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 08/27/2013 03:11 PM, Roy Bamford wrote:
> > On 2013.08.17 23:20, William Hubbs wrote:
> >> Council members,
> >>
> >> After looking over the documentation I know about [1] [2] [3], I 
> >> think
> >> it is safe to Say we are prepared to move forward with stating that
> >> the
> >> 	preparations for early boot mechanisms are complete.
> > 
> > [snip]
> > 
> >> Thanks,
> >>
> >> William
> >>
> >> [1] http://www.gentoo.org/doc/en/initramfs-guide.xml
> >> [2] http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-
> >> quickinstall.xml
> >> [3] https://wiki.gentoo.org/wiki/Early_Userspace_Mounting
> >> [4] https://bugs.gentoo.org/show_bug.cgi?id=481202
> >>
> > 
> > William,
> > 
> > If such a vote were to go in your favour, what are the next steps and 
> > the timescale(s) for these steps?
> > 
> > You clearly perceive the vote you seek as endorsing a plan of action 
> > relating to the /usr merge.
> 
> While the /usr merge does require people to use initramfs, using
> initramfs does not require a /usr merge.
> 
> Please, keep two completely separate topics separate like they are.  I
> am 1000% behind requiring initramfs, I couldn't possibly care less about
> /usr merge, in my eyes it's a hack to handle stupidity.

Rick is correct. I am not trying to force the /usr merge. That is a
totally separate topic.

All I'm asking the council to do in this vote is make sure that our
documentation for building initramfs is ready. Once that is done, bugs
like https://bugs.gentoo.org/show_bugs.cgi?id=443710 would be invalid
because we can just tell people to setup initramfs and point them to the
documentation.

The /usr merge is a separate topic, for another time.

William

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-28  1:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 22:20 [gentoo-project] rfc: separate /usr preparation vote William Hubbs
2013-08-18  6:32 ` Ulrich Mueller
2013-08-18 11:37   ` Rich Freeman
2013-08-19  2:48     ` William Hubbs
2013-08-19  3:10       ` Rich Freeman
2013-08-19  3:48         ` Rick "Zero_Chaos" Farina
2013-08-19 11:31           ` Rich Freeman
2013-08-19  6:19       ` Sven Vermeulen
2013-08-19  6:30       ` Ulrich Mueller
2013-08-19 13:35         ` Ian Stakenvicius
2013-08-18 13:08   ` Anthony G. Basile
2013-08-18 13:46     ` Rich Freeman
2013-08-19  0:18       ` Denis Dupeyron
2013-08-19  0:29         ` Rick "Zero_Chaos" Farina
2013-08-19  1:40       ` Anthony G. Basile
2013-08-19  1:57         ` Rich Freeman
2013-08-27 19:11 ` Roy Bamford
2013-08-27 19:30   ` Ian Stakenvicius
2013-08-28  0:46     ` Rich Freeman
2013-08-27 19:30   ` Rick "Zero_Chaos" Farina
2013-08-28  1:25     ` William Hubbs [this message]
2013-08-28 15:04       ` Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130828012501.GA6295@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox