From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] remove wraiths of 2up from FAQ and .gitignore
Date: Fri, 30 Oct 2015 03:00:14 -0700 [thread overview]
Message-ID: <20151030100014.GE4122@linux.vnet.ibm.com> (raw)
In-Reply-To: <1446197836-25128-1-git-send-email-sj38.park@gmail.com>
On Fri, Oct 30, 2015 at 06:37:16PM +0900, SeongJae Park wrote:
> Output have unified to perfbook.pdf from the commit
> 0835aa627d2accb1f39c5584ddb693cf31c57db2 (Remove 2up from Makefile).
> However, the wraiths of 2up still exist. This commit removes them from
> FAQ and gitignore.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good catch, applied, thank you!
Thanx, Paul
> ---
> .gitignore | 1 -
> FAQ.txt | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/.gitignore b/.gitignore
> index 7c9c46f..5df1646 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -34,7 +34,6 @@ RCS
> /Pieces
> /.Detritus
> /perfbook.ps
> -/perfbook-2up.ps
> perfbook_html/
>
> !/todo.txt
> diff --git a/FAQ.txt b/FAQ.txt
> index 631e18c..a698d3d 100644
> --- a/FAQ.txt
> +++ b/FAQ.txt
> @@ -1,7 +1,7 @@
> 1. OK, I have downloaded this stuff. What do I do now?
>
> A. Type "make" from the top-level directory. If all goes
> - well, this will produce a file named "perfbook-2up.pdf",
> + well, this will produce a file named "perfbook.pdf",
> which prints two virtual pages per physical page.
>
> 2. The Makefile cannot find pdflatex. What is it and where can I
> --
> 1.9.1
>
prev parent reply other threads:[~2015-10-30 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 9:37 [PATCH] remove wraiths of 2up from FAQ and .gitignore SeongJae Park
2015-10-30 10:00 ` Paul E. McKenney [this message]
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=20151030100014.GE4122@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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.