From: zhouzhouyi@gmail.com
To: paulmck@kernel.org, akiyks@gmail.com, perfbook@vger.kernel.org
Cc: 周洲仪 <8241764+zhouyizhousihai@user.noreply.gitee.com>,
"Zhouyi Zhou" <zhouzhouyi@gmail.com>
Subject: [PATCH perfbook] bib: make ref to git archive explicit
Date: Wed, 27 Dec 2023 10:49:54 +0800 [thread overview]
Message-ID: <1703645394-30331-1-git-send-email-zhouzhouyi@gmail.com> (raw)
From: 周洲仪 <8241764+zhouyizhousihai@user.noreply.gitee.com>
According to our Chinese version editor Yunjing Li's advice,
make reference to perfbook's git archive explicit.
Signed-off-by: Zhouyi Zhou<zhouzhouyi@gmail.com>
---
bib/syncrefs.bib | 8 ++++++++
howto/howto.tex | 2 +-
legal.tex | 5 ++---
3 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/bib/syncrefs.bib b/bib/syncrefs.bib
index 6ee50e3b..4f347488 100644
--- a/bib/syncrefs.bib
+++ b/bib/syncrefs.bib
@@ -2025,3 +2025,11 @@ Parallel Server on UNIX",
Month="September",
Note="Linux Plumbers Conference \url{https://lpc.events/event/16/contributions/1226/}",
}
+
+@unpublished{PaulmckPerfbookGit,
+ author="Paul E. McKenney",
+ title="Is Parallel Programming Hard, And, If So, What Can You Do About It? Git Archive",
+ year="2023",
+ note={\url{git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git}},
+ lastchecked="December 27, 2023",
+}
\ No newline at end of file
diff --git a/howto/howto.tex b/howto/howto.tex
index 55270cba..e7cd5f3c 100644
--- a/howto/howto.tex
+++ b/howto/howto.tex
@@ -226,7 +226,7 @@ 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~\cite{PaulmckPerfbookGit}.
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
diff --git a/legal.tex b/legal.tex
index f443df37..ca21ecaf 100644
--- a/legal.tex
+++ b/legal.tex
@@ -42,12 +42,11 @@ Source code is covered by various versions of the GPL\@.\footnote{
Some of this code is GPLv2-only, as it derives from the Linux kernel,
while other code is GPLv2-or-later.
See the comment headers of the individual source files within the
-CodeSamples directory in the git archive\footnote{
- \url{git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git}}
+CodeSamples directory in the git archive~\cite{PaulmckPerfbookGit}
for the exact licenses.
If you are unsure of the license for a given code fragment,
you should assume GPLv2-only.
Combined work {\textcopyright}~2005--\commityear\ by Paul E. McKenney.
Each individual contribution is copyright by its contributor at the time
-of contribution, as recorded in the git archive.
+of contribution, as recorded in the git archive~\cite{PaulmckPerfbookGit}.
--
2.34.1
next reply other threads:[~2023-12-27 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 2:49 zhouzhouyi [this message]
2023-12-27 4:53 ` [PATCH perfbook] bib: make ref to git archive explicit Akira Yokosawa
2023-12-27 5:59 ` Zhouyi Zhou
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=1703645394-30331-1-git-send-email-zhouzhouyi@gmail.com \
--to=zhouzhouyi@gmail.com \
--cc=8241764+zhouyizhousihai@user.noreply.gitee.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).