All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-cachefs@redhat.com,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-afs@lists.infradead.org
Subject: Re: [PATCH net-next 00/12] fscache: Fixes, traces and development
Date: Fri, 6 Apr 2018 11:32:11 -0700	[thread overview]
Message-ID: <CA+55aFx_fs7C6JAX_ORJ9MoXEp25LcXS0CUnK4aO4p=hQw6xOg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwKc1JzU6k=3R9n23HGXb5-BACT8pQ93rGTvgNjfa4ZHA@mail.gmail.com>

On Fri, Apr 6, 2018 at 11:21 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> No, but if you can redo the pull request part so that the diffstat I
> get will match the diffstat I see in the pull request, that would be
> good.

Oh, and can you please make sure there is a "[GIT PULL]" in the
subject line for your pull requests?

Particularly during the merge window (not so much later) I end up
having a separate filtered list of emails that I look at that mention
"git pull".

Your pull requests don't seem to match that, so your pull requests
don't actually even show up in my list of pending pull requests.

That doesn't mean that they get lost - it just tends to mean that I
don't necessarily see them during my busiest days of pulling. I
usually start my days off looking at emails in general, so I see
discussions and I see your emails, but then when I start actually
pulling I go to that list of pending pull requests, and never actually
pull your stuff.

That all changes the second week of the merge window when I generally
don't have a separate list of pull requests at all (because I've
gotten through the big pile of pending stuff), so the pull *does*
eventually happen, but it kind of gets delayed.

For example, yesterday when I was doing filesystem pulls (I try to
often group "similar areas" together), I did nfsd and f2fs. I would
have done your afs and fscache pulls while at it, but they didn't show
up in my pull request list, so I didn't..

So if you have that [GIT PULL] in the subject line, the pulls will
often be a bit timelier.

(Again, this is mainly just an issue for the merge window, but it
certainly doesn't hurt at other times).

                 Linus

  reply	other threads:[~2018-04-06 18:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 22:06 [PATCH net-next 00/12] fscache: Fixes, traces and development David Howells
2018-04-04 22:06 ` [PATCH 01/12] afs: Invalidate cache on server data change David Howells
2018-04-04 22:06 ` [PATCH 02/12] afs: Use the vnode ID uniquifier in the cache key not the aux data David Howells
2018-04-04 22:07 ` [PATCH 03/12] afs: Be more aggressive in retiring cached vnodes David Howells
2018-04-04 22:07 ` [PATCH 04/12] fscache, cachefiles: Fix checker warnings David Howells
2018-04-04 22:07 ` [PATCH 05/12] fscache: Pass the correct cancelled indications to fscache_op_complete() David Howells
2018-04-04 22:07 ` [PATCH 06/12] fscache: Detect multiple relinquishment of a cookie David Howells
2018-04-04 22:53   ` Linus Torvalds
2018-04-04 22:07 ` [PATCH 07/12] fscache: Fix hanging wait on page discarded by writeback David Howells
2018-04-04 22:07 ` [PATCH 08/12] fscache: Add tracepoints David Howells
2018-04-04 22:07 ` [PATCH 09/12] fscache: Add more tracepoints David Howells
2018-04-04 22:07 ` [PATCH 10/12] fscache: Attach the index key and aux data to the cookie David Howells
2018-04-04 22:07 ` [PATCH 11/12] fscache: Pass object size in rather than calling back for it David Howells
2018-04-04 22:08 ` [PATCH 12/12] fscache: Maintain a catalogue of allocated cookies David Howells
2018-04-04 22:10 ` [PATCH net-next 00/12] fscache: Fixes, traces and development David Howells
2018-04-06 14:44 ` David Howells
2018-04-06 18:21   ` Linus Torvalds
2018-04-06 18:32     ` Linus Torvalds [this message]
2018-04-06 21:02       ` Matthew Wilcox
2018-04-06 21:16         ` Linus Torvalds
2018-04-06 19:28     ` David Howells
2018-04-06 19:40       ` Linus Torvalds

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='CA+55aFx_fs7C6JAX_ORJ9MoXEp25LcXS0CUnK4aO4p=hQw6xOg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.