From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] VFS - the first pile
Date: Tue, 15 Mar 2011 22:18:18 +0000 [thread overview]
Message-ID: <20110315221818.GN22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110315213248.GL22723@ZenIV.linux.org.uk>
On Tue, Mar 15, 2011 at 09:32:48PM +0000, Al Viro wrote:
> Shortlog:
> Al Viro (45):
> compat breakage in preadv() and pwritev()
BTW, a question about rebases: is that kind of situation worth doing
a rebase of the queue/backmerge/etc.?
This commit sits in the base of that branch, with branchpoint at Mar 10;
the same thing had been applied in mainline at Mar 13. git merge does,
of course, handle it just fine; I guess I should've posted a pull request
back then instead of posting the patch - to be honest, I hadn't thought
about that.
What's the prefered way of dealing with such situations? Leave as is?
Rebase at the point where the patch went into mainline? Something else?
next prev parent reply other threads:[~2011-03-15 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 21:32 [git pull] VFS - the first pile Al Viro
2011-03-15 22:02 ` Sam Ravnborg
2011-03-15 22:18 ` Al Viro [this message]
2011-03-15 22:47 ` Linus Torvalds
2011-03-15 23:02 ` Al Viro
2011-03-16 6:19 ` Dave Chinner
2011-03-16 6:51 ` Al Viro
2011-03-16 7:21 ` Al Viro
2011-03-16 11:46 ` Theodore Tso
2011-03-16 13:07 ` Christoph Hellwig
2011-03-16 13:15 ` Al Viro
2011-03-16 13:18 ` Christoph Hellwig
2011-03-16 13:05 ` Christoph Hellwig
2011-03-16 13:10 ` Christoph Hellwig
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=20110315221818.GN22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).