[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwvKerkzigZmm0zrUTnsqDpJs0XBtX72Ltmek+_ic-KmA@mail.gmail.com>
Date: Wed, 25 Jul 2018 11:23:03 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Howells <dhowells@...hat.com>
Cc: kiran.modukuri@...il.com, linux-cachefs@...hat.com,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] fscache and cachefiles fixes
On Wed, Jul 25, 2018 at 11:18 AM David Howells <dhowells@...hat.com> wrote:
>
> Linus Torvalds <torvalds@...ux-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
Powered by blists - more mailing lists