On Thu, Sep 22, 2022 at 10:57:38AM -0700, Linus Torvalds wrote: > On Thu, Sep 22, 2022 at 9:27 AM Casey Schaufler <casey@xxxxxxxxxxxxxxxx> wrote: > > > > Could we please see the entire patch set on the LSM list? > > While I don't think that's necessarily wrong, I would like to point > out that the gitweb interface actually does make it fairly easy to > just see the whole patch-set. > > IOW, that > > https://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git/log/?h=fs.acl.rework > > that Christian pointed to is not a horrible way to see it all. Go to > the top-most commit, and it's easy to follow the parent links. > > It's a bit more work to see them in another order, but I find the > easiest way is actually to just follow the parent links to get the > overview of what is going on (reading just the commit messages), and > then after that you "reverse course" and use the browser back button > to just go the other way while looking at the details of the patches. > > And I suspect a lot of people are happier *without* large patch-sets > being posted to the mailing lists when most patches aren't necessarily > at all relevant to that mailing list except as context. The problem is also that it's impossible to please both parties here. A good portion of people doesn't like being flooded with patches they don't really care about and the other portion gets worked up when they only see a single patch. So honestly I just always make a judgement call based on the series. But b4 makes it so so easy to just retrieve the whole series. So even if I only receive a single patch and am curious then I just use b4. I've even got it integrated into mutt directly: # Pipe message to b4 to download patches and threads macro index,pager A "<pipe-message>b4 am --apply-cover-trailers --sloppy-trailers --add-my-sob --guess-base --check-newer-revisions --no-cache --quilt-ready <enter>" macro index,pager M "<pipe-message>b4 mbox <enter>"
