From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Leonardo Brás" <leobras.c@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Perfbook : Thanks!
Date: Tue, 31 Jan 2023 13:45:28 -0800 [thread overview]
Message-ID: <20230131214528.GY2948950@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <d49bc621da6f74e33cd41d5fc3d1e9ed17cba3bd.camel@gmail.com>
On Tue, Jan 31, 2023 at 06:09:50PM -0300, Leonardo Brás wrote:
> Hello Paul,
>
> I am a newbie Kernel Developer, and I was already a fan of your work on memory-
> barriers.txt.
>
> A couple weeks ago a friend of mine recommended reading perfbook, and sent me an
> older version (2011.01.02a). After reading a few pages I went on and found that
> the book had newer releases and is often updated and maintained with git, which
> got me really impressed.
>
> (I had a lot of work gone to waste on other books I found errors on, and
> perfbook's git workflow just make a lot of sense to me)
>
> Since it's a topic I am really interested in, and I noticed the book has updates
> from a couple days ago, I decided to install texinfo packages and compile a new
> version for me to start reading.
>
> I then noticed it would be nice to keep reading the latest version whenever an
> update came by, so I created a gitlab-ci to re-generate the book after a new
> commit / push: https://gitlab.com/linux-kernel/perfbook
>
> Is that ok if I keep this gitlab repository re-generating the book?
>
> Is a gitlab-ci of any use for you?
> If so, I can send it as a patch (a single .gitlab-ci.yaml file), and refine it
> according to your needs.
>
> Thanks for keeping the book updated!
Hello, Leonardo, and glad you like the book!
On the automated CI, I cant't think of a problems with it. In fact, in
my experience, automated testing is usually a good thing. I am adding
the perfbook email list in case others have advice or other guidance.
Just out of curiosty, are you thinking of automating tests of the
sample code as well as of the LaTeX builds?
Thanx, Paul
next parent reply other threads:[~2023-01-31 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d49bc621da6f74e33cd41d5fc3d1e9ed17cba3bd.camel@gmail.com>
2023-01-31 21:45 ` Paul E. McKenney [this message]
2023-02-01 2:19 ` Perfbook : Thanks! Leonardo Brás
2023-02-01 4:15 ` Paul E. McKenney
[not found] ` <093f3237c3dbfe0daa8a35040dcd5c114be153bb.camel@gmail.com>
[not found] ` <20230201142318.GD2948950@paulmck-ThinkPad-P17-Gen-1>
2023-02-01 20:29 ` Leonardo Brás
2023-02-01 22:10 ` 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=20230131214528.GY2948950@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=leobras.c@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).