From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] FAQ-BUILD.txt: Fix misinfomation crept in wordsmithing
Date: Fri, 24 Mar 2017 11:12:39 -0700 [thread overview]
Message-ID: <20170324181239.GJ3637@linux.vnet.ibm.com> (raw)
In-Reply-To: <c7a6f457-3914-9e5e-a42a-29e9b8f67b77@gmail.com>
On Fri, Mar 24, 2017 at 07:20:28AM +0900, Akira Yokosawa wrote:
> >From f7c19259ce4182688d94853c7fddc092011e802b Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Fri, 24 Mar 2017 07:03:54 +0900
> Subject: [PATCH] FAQ-BUILD.txt: Fix misinformation crept in by wordsmithing
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Hello, Akira,
I tried applying all three, then just the two in the series, and either
way, "git am" complains about not being able to apply the patches.
I did merge my wordsmithing into your original patch, which might be
the source of the problem. Could you please check?
Thanx, Paul
> ---
> Hi Paul,
>
> Thanks for the wordsmithing.
> There were a few things I want fix.
> How about this patch?
>
> Thanks, Akira
>
> FAQ-BUILD.txt | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/FAQ-BUILD.txt b/FAQ-BUILD.txt
> index c772e8f..a47eef6 100644
> --- a/FAQ-BUILD.txt
> +++ b/FAQ-BUILD.txt
> @@ -91,8 +91,8 @@
> A. The simplest approach is to upgrade to a recent TeX
> distribution such as TeX Live 2016. Upgrading your Linux
> distribution (e.g. to Ubuntu Xenial) is one way to
> - upgrade to TeX Live 2016, and might have many other
> - benefits as well.
> + upgrade TeX Live (to 2015 on Xenial), and might have many
> + other benefits as well.
>
> However, if you prefer to manually install individual
> packages, refer to "Method 3" in:
> @@ -105,9 +105,10 @@
> http://tex.stackexchange.com/questions/88423/
>
> Note: If available, you can use the <package>.tds.zip,
> - which will automatically put the files in the right place.
> - Note that font packages should be copied to the TEXMFLOCAL
> - directory rather than to the TEXFMHOME directory.
> + which will automatically put the files in a relatively
> + right place. Note that font packages should be copied to
> + the TEXMFLOCAL directory rather than to the TEXFMHOME
> + directory.
>
> Following is a list of links to optional packages as of
> March 2017:
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-03-24 18:12 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 ` [PATCH v2 0/2] Follow up patches to FAQ-BUILD update Akira Yokosawa
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 ` Paul E. McKenney [this message]
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=20170324181239.GJ3637@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox