public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: sfr@canb.auug.org.au, Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PULL/RFC] Doc tree moves: use more sub-directory structure
Date: Thu, 13 Nov 2008 13:51:16 -0800	[thread overview]
Message-ID: <491CA154.6020609@oracle.com> (raw)

RFC part:  when is the best time to request a pull of this git tree?
In the -rc1 merge window or some other time?

[It currently applies cleanly to linux-next and with only some of my
Documentation/ changes to mmotm.]


As a git novice, it's quite possible (or likely) that I did
something wrong here...


<trial run>


Please pull from

	git://git.kernel.org/pub/scm/linux/kernel/git/rdunlap/linux-docs doc-subdirs

to get these changes:

 Documentation/00-INDEX                      |   42 +-------------------------
 Documentation/PCI/00-INDEX                  |    2 +
 Documentation/{ => PCI}/MSI-HOWTO.txt       |    0
 Documentation/blockdev/00-INDEX             |   16 ++++++++++
 Documentation/{ => blockdev}/README.DAC960  |    0
 Documentation/{ => blockdev}/cciss.txt      |    0
 Documentation/{ => blockdev}/cpqarray.txt   |    0
 Documentation/{ => blockdev}/floppy.txt     |    0
 Documentation/{ => blockdev}/nbd.txt        |    0
 Documentation/{ => blockdev}/paride.txt     |    0
 Documentation/{ => blockdev}/ramdisk.txt    |    0
 Documentation/ioctl/00-INDEX                |   10 ++++++
 Documentation/{ => ioctl}/ioctl-number.txt  |    0
 Documentation/kernel-parameters.txt         |   24 +++++++-------
 Documentation/serial/00-INDEX               |   24 +++++++++++++++
 Documentation/{ => serial}/README.cycladesZ |    0
 Documentation/{ => serial}/computone.txt    |    2 +-
 Documentation/{ => serial}/digiepca.txt     |    0
 Documentation/{ => serial}/hayes-esp.txt    |    0
 Documentation/{ => serial}/moxa-smartio     |    0
 Documentation/{ => serial}/riscom8.txt      |    0
 Documentation/{ => serial}/rocket.txt       |    0
 Documentation/{ => serial}/specialix.txt    |    0
 Documentation/{ => serial}/stallion.txt     |    0
 Documentation/{ => serial}/sx.txt           |    0
 Documentation/{ => serial}/tty.txt          |    0
 drivers/block/Kconfig                       |   29 +++++++++---------
 drivers/block/floppy.c                      |    2 +-
 drivers/char/Kconfig                        |   24 +++++++-------
 drivers/char/specialix.c                    |    2 +-
 30 files changed, 96 insertions(+), 81 deletions(-)
 rename Documentation/{ => PCI}/MSI-HOWTO.txt (100%)
 create mode 100644 Documentation/blockdev/00-INDEX
 rename Documentation/{ => blockdev}/README.DAC960 (100%)
 rename Documentation/{ => blockdev}/cciss.txt (100%)
 rename Documentation/{ => blockdev}/cpqarray.txt (100%)
 rename Documentation/{ => blockdev}/floppy.txt (100%)
 rename Documentation/{ => blockdev}/nbd.txt (100%)
 rename Documentation/{ => blockdev}/paride.txt (100%)
 rename Documentation/{ => blockdev}/ramdisk.txt (100%)
 create mode 100644 Documentation/ioctl/00-INDEX
 rename Documentation/{ => ioctl}/ioctl-number.txt (100%)
 create mode 100644 Documentation/serial/00-INDEX
 rename Documentation/{ => serial}/README.cycladesZ (100%)
 rename Documentation/{ => serial}/computone.txt (99%)
 rename Documentation/{ => serial}/digiepca.txt (100%)
 rename Documentation/{ => serial}/hayes-esp.txt (100%)
 rename Documentation/{ => serial}/moxa-smartio (100%)
 rename Documentation/{ => serial}/riscom8.txt (100%)
 rename Documentation/{ => serial}/rocket.txt (100%)
 rename Documentation/{ => serial}/specialix.txt (100%)
 rename Documentation/{ => serial}/stallion.txt (100%)
 rename Documentation/{ => serial}/sx.txt (100%)
 rename Documentation/{ => serial}/tty.txt (100%)

                 reply	other threads:[~2008-11-13 21:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=491CA154.6020609@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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