From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] acl updates for v6.2
Date: Tue, 13 Dec 2022 10:09:22 +0100 [thread overview]
Message-ID: <20221213090922.svty4cb4jmkaccgp@wittgenstein> (raw)
In-Reply-To: <CAHk-=witvjWrYOqbgURdeH7cv7bkVT5O2wd_HcoY6L-3_3yK8A@mail.gmail.com>
On Mon, Dec 12, 2022 at 06:56:59PM -0800, Linus Torvalds wrote:
> On Mon, Dec 12, 2022 at 3:19 AM Christian Brauner <brauner@kernel.org> wrote:
> >
> > For a long and detailed
> > explanation for just some of the issues [1] provides a good summary.
>
> There is no link [1].
>
> > A few implementation details:
> >
> > * The series makes sure to retain exactly the same security and integrity module
> > permission checks. See [2] for annotated callchains.
>
> There is no link [2].
>
> This was an extensive changelog for my merge commit, so it's all fine
> and I've pulled it, but it does look like some pieces were either
> missing, or there was a bit of a cut-and-paste from previous
> explanations without the links..
Bah, there was a single stray word "mainline" in the pr after the
/* Conflicts */ section because I copied it over a small (relatively
uninteresting) paragraph.
So the two missing links are:
[1]: https://lore.kernel.org/all/20220801145520.1532837-1-brauner@kernel.org
[2]: https://gist.github.com/brauner/12c795b93a05dc3b3056b1982549a633
they are also listed in the cover letter for the series.
I think I might need a script to look for missing links in the pull
request. I've had a missing link before. Hopefully I'll get around to
this.
About the cut-and-paste: What follows is just my personal
theory/preference but I think it helps to understand how the pr message
come together. If the series is a self-contained topic and not a
collection of a pile of commits than I aim for the description given in
the cover letter and the description given in the merge/pull request
message to be almost indistinguishable. So the cover letter I keep in
git edit --branch-description will morph into the merge/pull request
message.
So I often will try to write the cover letter in a form that is suitable
for the merge commit. Of course, the cover letter will often contain
additional technical information that might not be suitable for the
cover letter. Such sections will then be cut our or rewritten for the pr
message.
Christian
next prev parent reply other threads:[~2022-12-13 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:19 Christian Brauner
2022-12-13 2:56 ` Linus Torvalds
2022-12-13 9:09 ` Christian Brauner [this message]
2022-12-13 3:49 ` pr-tracker-bot
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=20221213090922.svty4cb4jmkaccgp@wittgenstein \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®