All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH v2 0/2] Follow up patches to FAQ-BUILD update
Date: Fri, 24 Mar 2017 22:48:33 +0900	[thread overview]
Message-ID: <7dd80f92-b8e7-3912-9bca-e59100e4665d@gmail.com> (raw)
In-Reply-To: <c7a6f457-3914-9e5e-a42a-29e9b8f67b77@gmail.com>

From dd65cd3918b33e9bd267661ea697b39755be72a1 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Fri, 24 Mar 2017 22:42:36 +0900
Subject: [PATCH v2 0/2] Follow up patches to FAQ-BUILD update

(I messed up thread relation and made some typo. Let me do it again.)

Hi Paul,

This is a nitpick patch set to the update of FAQ-BUILD.txt.

Patch 1 is a typo fix relative to the patch "FAQ-BUILD.txt:
Fix misinformation crept in wordsmithing" I sent earlier.

Patch 2 is to detect another build error condition to happen
when you fail to update font-map database after manually
installing a font package.

                            Thanks, Akira
--

Akira Yokosawa (2):
  FAQ-BUILD.txt: Typo fix
  Add another build error check

 FAQ-BUILD.txt              | 2 +-
 utilities/runfirstlatex.sh | 6 ++++++
 utilities/runlatex.sh      | 6 ++++++
 3 files changed, 13 insertions(+), 1 deletion(-)

-- 
2.7.4



  parent reply	other threads:[~2017-03-24 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 13:03 [PATCH] FAQ-BUILD.txt: Append reference to manual LaTeX package install Akira Yokosawa
2017-03-23 15:35 ` Paul E. McKenney
2017-03-23 22:20   ` [PATCH] FAQ-BUILD.txt: Fix misinfomation crept in wordsmithing Akira Yokosawa
2017-03-24 13:17     ` [PATCH 0/2] Follow up patches to FAQ-BUILD update Akira Yokosawa
2017-03-24 13:19       ` [PATCH 1/2] FAQ-BUILD.txt: Typo fix Akira Yokosawa
2017-03-24 13:20     ` [PATCH 2/2] Add another build error check Akira Yokosawa
2017-03-24 13:48     ` Akira Yokosawa [this message]
2017-03-24 13:49       ` [PATCH v2 1/2] FAQ-BUILD.txt: Typo fix Akira Yokosawa
2017-03-24 13:51       ` [PATCH v2 2/2] Add another build error check Akira Yokosawa
2017-03-24 18:12     ` [PATCH] FAQ-BUILD.txt: Fix misinfomation crept in wordsmithing Paul E. McKenney
2017-03-24 22:52       ` [PATCH v3 0/2] Follow up patches to FAQ-BUILD update Akira Yokosawa
2017-03-24 23:00       ` [PATCH v4 " Akira Yokosawa
2017-03-24 23:02         ` [PATCH v4 1/2] FAQ-BUILD.txt: Fix misinformation crept in wordsmithing Akira Yokosawa
2017-03-24 23:03         ` [PATCH v4 2/2] Add another build error check Akira Yokosawa
2017-03-25  0:46         ` [PATCH v4 0/2] Follow up patches to FAQ-BUILD update Paul E. McKenney

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=7dd80f92-b8e7-3912-9bca-e59100e4665d@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=perfbook@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.