From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: hpa <hpa@zytor.com>
Subject: Re: x86: move x86-specific documentation into Documentation/x86
Date: Wed, 16 Jul 2008 09:53:53 -0700 [thread overview]
Message-ID: <20080716095353.9c26a0c5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200807142239.m6EMdCED028677@hera.kernel.org>
On Mon, 14 Jul 2008 22:39:12 GMT Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=23deb06821442506615f34bd92ccd6a2422629d7
> Commit: 23deb06821442506615f34bd92ccd6a2422629d7
> Parent: 4039feb5bae72a5fed9ba6bc1a9cfd8dfe0a8613
> Author: H. Peter Anvin <hpa@zytor.com>
> AuthorDate: Fri May 30 17:19:03 2008 -0700
> Committer: H. Peter Anvin <hpa@zytor.com>
> CommitDate: Fri May 30 17:19:03 2008 -0700
>
> x86: move x86-specific documentation into Documentation/x86
>
> The current organization of the x86 documentation makes it appear as
> if the "i386" documentation doesn't apply to x86-64, which is does.
> Thus, move that documentation into Documentation/x86, and move the
> x86-64-specific stuff into Documentation/x86/x86_64 with the eventual
> goal to move stuff that isn't actually 64-bit specific back into
> Documentation/x86.
Thanks for doing this.
How about this also?
git mv Documentation/mtrr.txt Documentation/x86/mtrr.txt
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
parent reply other threads:[~2008-07-16 16:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200807142239.m6EMdCED028677@hera.kernel.org>]
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=20080716095353.9c26a0c5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®