From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: paulmck@kernel.org, perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook v4] howto: make ref to git archive explicit
Date: Wed, 27 Dec 2023 18:53:37 +0800 [thread overview]
Message-ID: <CAABZP2y3uUT+6hqy=+Na=KzO2xCe0+jVqv2MEzu20uRCZTCZhw@mail.gmail.com> (raw)
In-Reply-To: <59dc36ad-16f3-4424-b698-0a1678c3a48e@gmail.com>
On Wed, Dec 27, 2023 at 6:34 PM Akira Yokosawa <akiyks@gmail.com> wrote:
>
> On Wed, 27 Dec 2023 17:34:25 +0800, zhouzhouyi@gmail.com wrote:
> > From: Zhouyi Zhou <zhouzhouyi@gmail.com>
> >
> > Make "git archive" in answer to Quick Quiz 1.3 more explicit, so that reader can easily know where
> > "git archive" is.
>
> Now that this patch adds just a footnote mentioning Section 1.5,
> commit log can use some adjustments.
>
> How about:
>
> Make "git archive" in answer to Quick Quiz 1.3 more explicit by
> adding a footnote, so that a first-time reader, who have never
> read Section 1.5, can easily know how to clone the Git repo and
> build PDFs.
>
The revised version makes the commit log more clear and elegant! I
will submit the 5th version.
Thank you for your beautiful work！
> That said, I'm beginning to wonder how many of first-time readers
> would bother trying -nq builds without having got annoyed by those
> lots of QQz's in perfbook. ;-)
Haha, that's a good point! It's indeed a challenge for first-timers to
dive into nq builds, especially with the complexities
in installing a latex environment and various fonts in Linux desktop
;-) It's quite a learning curve, and it's rewarding in the end.
>
> >
> > Suggested-by: Akira Yokosawa <akiyks@gmail.com>
> > Signed-off-by: Zhouyi Zhou<zhouzhouyi@gmail.com>
>
> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
>
> Thanks, Akira
Thanks, Zhouyi
>
> > ---
> > Hi Akira
> >
> > Thank you for your valuable suggestions and guidances, I learned a lot
> > during this process ;-)
> >
> > And I invoke make -j 20 in my ubuntu 22.04, everything works great!
> >
> > Our editor Yunjing Li is still too modest to provide her email, sorry.
> >
> > Thanks for your patient and hard work.
> >
> > Thanks
> > Zhouyi
> > --
> > howto/howto.tex | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/howto/howto.tex b/howto/howto.tex
> > index 55270cba..8d678644 100644
> > --- a/howto/howto.tex
> > +++ b/howto/howto.tex
> > @@ -226,7 +226,9 @@ Here are a few possible strategies:
> > only a blank sheet of paper.
> > \item If you find the Quick Quizzes distracting but impossible
> > to ignore, you can always clone the \LaTeX{} source for
> > - this book from the git archive.
> > + this book from the git archive.\footnote{
> > + See \cref{sec:howto:Whose Book Is This?}
> > + for instructions to do this.}
> > You can then run the command \co{make nq}, which will
> > produce a \co{perfbook-nq.pdf}.
> > This PDF contains unobtrusive boxed tags where the Quick Quizzes
prev parent reply other threads:[~2023-12-27 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 9:34 [PATCH -perfbook v4] howto: make ref to git archive explicit zhouzhouyi
2023-12-27 10:34 ` Akira Yokosawa
2023-12-27 10:53 ` Zhouyi Zhou [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='CAABZP2y3uUT+6hqy=+Na=KzO2xCe0+jVqv2MEzu20uRCZTCZhw@mail.gmail.com' \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).