From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] fs idmapped updates for v6.2
Date: Mon, 12 Dec 2022 19:40:29 -0800 [thread overview]
Message-ID: <CAHk-=wj+tqv2nyUZ5T5EwYWzDAAuhxQ+-DA2nC9yYOTUo5NOPg@mail.gmail.com> (raw)
In-Reply-To: <20221212131915.176194-1-brauner@kernel.org>
On Mon, Dec 12, 2022 at 5:19 AM Christian Brauner <brauner@kernel.org> wrote:
>
> Please note the tag contains all other branches for this cycle merged in.
Well, considering that the explanation basically assumed I had already
merged those (and I had), I wish you also had made the diffstat and
the shortlog reflect that.
As it was, now the diffstat and shortlog ends up containing not what
this last pull request brought in, but what they *all* brought in...
I'm also not super-happy with how ugly your history for this branch
was. You had literally merged the acl rework branch three times - at
different points of that branch.
Do we have other ugly history in the tree? Yes. But we've been getting
better. This was _not_ one of those "getting better" moments.
Oh well. I can see what you wanted to do, and I agree with the end
result, I just don't particularly like how this was done.
I've pulled it.
Linus
next prev parent reply other threads:[~2022-12-13 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:19 [GIT PULL] fs idmapped updates for v6.2 Christian Brauner
2022-12-13 3:40 ` Linus Torvalds [this message]
2022-12-13 9:40 ` Christian Brauner
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='CAHk-=wj+tqv2nyUZ5T5EwYWzDAAuhxQ+-DA2nC9yYOTUo5NOPg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).