From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Some Updates to the Quick Install Guide
Date: Sat, 19 Jan 2013 20:59:26 +0000 [thread overview]
Message-ID: <20130119205926.GA26866@gentoo.org> (raw)
In-Reply-To: <20130117045927.GA8473@Positve>
On Wed, Jan 16, 2013 at 11:59:27PM -0500, Daniel Meltzer wrote:
> I recently reinstalled gentoo after a long hiatus, and noticed that a
> lot of documentation has aged a bit over time and grown out of sync.
> Being that I dislike this, I'm setting out to try and clean some of it
> up. My first project was updating the quickinstall guide to reflect
> some of the changes that have been made to the handbook over the last
> few years. I doubt I have covered all of them, but I think this takes
> care of the glaring differences. I'm going to send these along via
> the fancy git commands this time. If you want me to make them go to
> bugzilla in the future I'll be happy to do that, this just seemed like
> a more approachable first step.
>
> I think it would make sense to turn this into a x86/amd64 combined
> guide as well, I haven't started on that yet but with the prevelance
> of 64bit systems these days the x86 is kind of falling by the wayside.
> Please take a look at these patches, and let me know what you think.
> I will send more as time permits.
Hi Daniel
Thanks for the patches. I've applied them to the repo and committed. I did
remove the note regarding developer profiles; I think in a quickinstall
guide it doesn't serve its purpose fully (the quickinstall guide is/was
meant to provide a small resource for experienced users to use as a, well,
quick reference).
Wkr,
Sven Vermeulen
prev parent reply other threads:[~2013-01-19 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 4:59 [gentoo-doc] Some Updates to the Quick Install Guide Daniel Meltzer
2013-01-19 20:59 ` Sven Vermeulen [this message]
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=20130119205926.GA26866@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-doc@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