From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: the second vfs pile - rebase or no rebase?
Date: Wed, 1 Aug 2012 10:30:41 -0700 [thread overview]
Message-ID: <CA+55aFwuzzNTMCu97oroCqpsA7qk7E7iFTrzOR=n4yMmW1TqdQ@mail.gmail.com> (raw)
In-Reply-To: <20120801151318.GH6481@ZenIV.linux.org.uk>
On Wed, Aug 1, 2012 at 8:13 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Alternatively, I can rebase the damn thing; up to you.
Oh, no. Those conflicts were trivial - I appreciate your description
of them, but they were simple enough that you didn't even have to
mention them. I'd *much* rather handle a few conflicts than have the
rebase dance with the problems that entails.
Linus
prev parent reply other threads:[~2012-08-01 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 15:13 the second vfs pile - rebase or no rebase? Al Viro
2012-08-01 17:30 ` Linus Torvalds [this message]
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+55aFwuzzNTMCu97oroCqpsA7qk7E7iFTrzOR=n4yMmW1TqdQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).