From: Ben Minerds <puzzleduck@gmail.com>
To: greg@kroah.com, rob@landley.net
Cc: Ben Minerds <PuZZleDucK@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] Documentation: Updating docs and links relating to patches.
Date: Thu, 23 May 2013 22:49:52 +1000 [thread overview]
Message-ID: <cover.1369312746.git.PuZZleDucK@gmail.com> (raw)
This patch series 1. adds "the perfect patch" doc 2. adds "submission format"
doc 3. update refs to perfect-patch 4. fix link in perfect patch 5. update
refs to sub-format 6. fix source ref in perfect patch 7. reformat submission
format doc 8. move other documents into patch sub directory.
Ben Minerds (8):
Documentation: Adding "The Perfect Patch" by Andrew Morton
Documentation: Adding "Linux Kernel Patch Submission Format"
Documentation: Replacing references to broken perfect patch URL
Documentation: Replacing reference to broken perfect patch URL
Documentation: Replacing reference to broken submission format URL
Documentation: Updating a broken link in "the perfect patch"
Documentation: Reformatting "Linux Kernel Patch Submission Format"
Documentation: Move other patch related document
Documentation/HOWTO | 12 +-
Documentation/SubmittingPatches | 743 ---------------------
Documentation/applying-patches.txt | 454 -------------
.../patches/Patch-Submission-Format.txt | 131 ++++
.../development-process/patches/SubmittingPatches | 743 +++++++++++++++++++++
.../patches/The-Perfect-Patch.txt | 167 +++++
.../patches/applying-patches.txt | 454 +++++++++++++
Documentation/ja_JP/HOWTO | 10 +-
Documentation/ja_JP/SubmittingPatches | 4 +-
Documentation/ko_KR/HOWTO | 6 +-
Documentation/zh_CN/HOWTO | 6 +-
Documentation/zh_CN/SubmittingPatches | 4 +-
12 files changed, 1516 insertions(+), 1218 deletions(-)
delete mode 100644 Documentation/SubmittingPatches
delete mode 100644 Documentation/applying-patches.txt
create mode 100644 Documentation/development-process/patches/Patch-Submission-Format.txt
create mode 100644 Documentation/development-process/patches/SubmittingPatches
create mode 100644 Documentation/development-process/patches/The-Perfect-Patch.txt
create mode 100644 Documentation/development-process/patches/applying-patches.txt
--
1.8.1.2
next reply other threads:[~2013-05-23 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 12:49 Ben Minerds [this message]
2013-05-23 12:49 ` [PATCH 1/8] Documentation: Adding "The Perfect Patch" by Andrew Morton Ben Minerds
2013-05-23 17:15 ` Dave Jones
2013-05-24 4:10 ` Rob Landley
2013-05-24 4:16 ` Joe Perches
2013-05-23 12:49 ` [PATCH 2/8] Documentation: Adding "Linux Kernel Patch Submission Format" Ben Minerds
2013-05-24 4:12 ` Rob Landley
2013-05-23 12:49 ` [PATCH 3/8] Documentation: Replacing references to broken perfect patch URL Ben Minerds
2013-05-23 12:49 ` [PATCH 4/8] Documentation: Replacing reference " Ben Minerds
2013-05-23 12:49 ` [PATCH 5/8] Documentation: Replacing reference to broken submission format URL Ben Minerds
2013-05-24 4:16 ` Rob Landley
2013-05-23 12:49 ` [PATCH 6/8] Documentation: Updating a broken link in "the perfect patch" Ben Minerds
2013-05-24 4:21 ` Rob Landley
2013-05-23 12:49 ` [PATCH 7/8] Documentation: Reformatting "Linux Kernel Patch Submission Format" Ben Minerds
2013-05-23 12:50 ` [PATCH 8/8] Documentation: Move other patch related document Ben Minerds
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=cover.1369312746.git.PuZZleDucK@gmail.com \
--to=puzzleduck@gmail.com \
--cc=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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