From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: kiran.modukuri@gmail.com, linux-cachefs@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] fscache and cachefiles fixes
Date: Wed, 25 Jul 2018 11:23:03 -0700 [thread overview]
Message-ID: <CA+55aFwvKerkzigZmm0zrUTnsqDpJs0XBtX72Ltmek+_ic-KmA@mail.gmail.com> (raw)
In-Reply-To: <25183.1532542685@warthog.procyon.org.uk>
On Wed, Jul 25, 2018 at 11:18 AM David Howells <dhowells@redhat.com> wrote:
>
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> > Why do they have commit times literally *minutes* before your email to
> > ask me to pull?
>
> I split the first patch into two because it had two more-or-less independent
> changes and it made it easier to describe them separately.
This didn't explain the background before that happened.
I really want the warm and fuzzies about things, and when I see
something being changed just minutes before, something like
"I did a rebase becasue XYZ, but this was around in linux-next for a
week before that without problems"
tells me not only why the times are so recent, but also tells me that
I really shouldn't worry because so-and-so.
Linus
next prev parent reply other threads:[~2018-07-25 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:02 [GIT PULL] fscache and cachefiles fixes David Howells
2018-07-25 18:13 ` Linus Torvalds
2018-07-25 18:18 ` David Howells
2018-07-25 18:23 ` Linus Torvalds [this message]
2018-07-25 19:31 ` David Howells
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+55aFwvKerkzigZmm0zrUTnsqDpJs0XBtX72Ltmek+_ic-KmA@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=kiran.modukuri@gmail.com \
--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 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).