From: David Howells <email@example.com>
To: Linus Torvalds <firstname.lastname@example.org>
Cc: email@example.com, Matthew Wilcox <firstname.lastname@example.org>,
Jeff Layton <email@example.com>,
David Wysochanski <firstname.lastname@example.org>,
Anna Schumaker <email@example.com>,
Trond Myklebust <firstname.lastname@example.org>,
Steve French <email@example.com>,
Dominique Martinet <firstname.lastname@example.org>,
Alexander Viro <email@example.com>,
firstname.lastname@example.org, CIFS <email@example.com>,
"open list:NFS, SUNRPC, AND..." <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: [GIT PULL] fscache: I/O API modernisation and netfs helper library
Date: Thu, 11 Feb 2021 23:20:46 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Linus Torvalds <email@example.com> wrote:
> Also, honestly, I really *REALLY* want your commit messages to talk
> about who has been cc'd, who has been part of development, and point
> to the PUBLIC MAILING LISTS WHERE THAT DISCUSSION WAS TAKING PLACE, so
> that I can actually see that "yes, other people were involved"
Most of the development discussion took place on IRC and waving snippets of
code about in pastebin rather than email - the latency of email is just too
high. There's not a great deal I can do about that now as I haven't kept IRC
logs. I can do that in future if you want.
> No, I don't require this in general, but exactly because of the
> history we have, I really really want to see that. I want to see a
> Link: https://lore.kernel.org/r/....
I can add links to where I've posted the stuff for review. Do you want this
on a per-patch basis or just in the cover for now?
Also, do you want things like these:
which pertain to the overall fscache rewrite, but where the relevant changes
didn't end up included in this particular patchset? Or this:
where someone was testing the overall patchset of which this is a subset?
> and the Cc's - or better yet, the Reviewed-by's etc - so that when I
> get a pull request, it really is very obvious to me when I look at it
> that others really have been involved.
> So if I continue to see just
> Signed-off-by: David Howells <firstname.lastname@example.org>
> at the end of the commit messages, I will not pull.
> Yes, in this thread a couple of people have piped up and said that
> they were part of the discussion and that they are interested, but if
> I have to start asking around just to see that, then it's too little,
> too late.
> No more of this "it looks like David Howells did things in private". I
> want links I can follow to see the discussion, and I really want to
> see that others really have been involved.
I can go and edit in link pointers into the existing patches if you want and
add Jeff's Review-and-tested-by into the appropriate ones. You would be able
to compare against the existing tag, so it wouldn't entirely invalidate the
Also, do you want links inserting into all the patches of the two keyrings
pull requests I've sent you?
next prev parent reply other threads:[~2021-02-11 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 16:09 [GIT PULL] fscache: I/O API modernisation and netfs helper library David Howells
2021-02-09 19:06 ` Linus Torvalds
2021-02-09 19:45 ` Jeff Layton
2021-02-09 20:21 ` Matthew Wilcox
2021-02-09 21:19 ` Linus Torvalds
2021-02-09 21:55 ` David Howells
2021-02-10 16:36 ` David Howells
2021-02-09 21:25 ` David Howells
2021-02-09 22:42 ` David Wysochanski
2021-02-09 21:10 ` David Howells
2021-02-10 16:29 ` David Howells
2021-02-10 16:33 ` David Howells
2021-02-10 20:43 ` Linus Torvalds
2021-02-11 22:38 ` David Howells
2021-02-11 23:20 ` David Howells [this message]
2021-02-12 16:40 ` David Wysochanski
2021-02-13 1:05 ` Linus Torvalds
2021-02-15 0:22 ` David Howells
2021-02-15 1:01 ` Linus Torvalds
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).