linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net, minchan@kernel.org
Cc: mchehab@s-opensource.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v2 00/12] Fix and update HOWTO Korean translation
Date: Tue,  1 Nov 2016 05:27:09 +0900	[thread overview]
Message-ID: <20161031202721.8068-1-sj38.park@gmail.com> (raw)

This patchset applies ReST conversion effort for HOWTO document to its Korean
translation.  It also contains fixup of trivial nitpicks in the document and
the translation.

Changes from v1:
- Rebased on next-20161028
  The base version contains commit 186128f75392 ("docs-rst: add documents to
  development-process")

SeongJae Park (12):
  Documentation/process/howto: Mark subsection in suggested format
  ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds
  ko_KR/HOWTO: Fix subtitles style
  ko_KR/HOWTO: Update obsolete link to bugzilla faq
  ko_KR/HOWTO: Convert to ReST notation
  ko_KR/HOWTO: Add cross-references to other documents
  ko_KR/HOWTO: Update information about generating documentation
  ko_KR/HOWTO: Improve some markups to make it visually better
  ko_KR/HOWTO: Adjust external link references
  ko_KR/HOWTO: Clean up bare :: lines
  ko_KR/HOWTO: Add whitespace between URL and text
  ko_KR/HOWTO: Mark subsection in suggested format

 Documentation/ko_KR/HOWTO       | 162 ++++++++++++++++++++++++++--------------
 Documentation/process/howto.rst |  15 ++--
 2 files changed, 117 insertions(+), 60 deletions(-)

-- 
2.10.0

             reply	other threads:[~2016-10-31 20:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 20:27 SeongJae Park [this message]
2016-10-31 20:27 ` [PATCH v2 01/12] Documentation/process/howto: Mark subsection in suggested format SeongJae Park
2016-10-31 20:27 ` [PATCH v2 02/12] ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds SeongJae Park
2016-10-31 20:27 ` [PATCH v2 03/12] ko_KR/HOWTO: Fix subtitles style SeongJae Park
2016-10-31 20:27 ` [PATCH v2 04/12] ko_KR/HOWTO: Update obsolete link to bugzilla faq SeongJae Park
2016-10-31 20:27 ` [PATCH v2 05/12] ko_KR/HOWTO: Convert to ReST notation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 06/12] ko_KR/HOWTO: Add cross-references to other documents SeongJae Park
2016-10-31 20:27 ` [PATCH v2 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 08/12] ko_KR/HOWTO: Improve some markups to make it visually better SeongJae Park
2016-10-31 20:27 ` [PATCH v2 09/12] ko_KR/HOWTO: Adjust external link references SeongJae Park
2016-10-31 20:27 ` [PATCH v2 10/12] ko_KR/HOWTO: Clean up bare :: lines SeongJae Park
2016-10-31 20:27 ` [PATCH v2 11/12] ko_KR/HOWTO: Add whitespace between URL and text SeongJae Park
2016-10-31 20:27 ` [PATCH v2 12/12] ko_KR/HOWTO: Mark subsection in suggested format SeongJae Park
2016-11-06 18:21 ` [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-11-06 20:45   ` Jonathan Corbet
2016-11-08  0:05 ` Jonathan Corbet
2016-11-08  1:30   ` SeongJae Park

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=20161031202721.8068-1-sj38.park@gmail.com \
    --to=sj38.park@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=minchan@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;
as well as URLs for NNTP newsgroup(s).