From: Al Viro <viro@ZenIV.linux.org.uk>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Merge of the 'write_inode' branch from the VFS tree
Date: Fri, 5 Mar 2010 18:29:24 +0000 [thread overview]
Message-ID: <20100305182924.GY30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1267812155.5174.9.camel@localhost.localdomain>
On Fri, Mar 05, 2010 at 01:02:35PM -0500, Trond Myklebust wrote:
> On Fri, 2010-03-05 at 15:48 +0000, Al Viro wrote:
>
> > Or I can do a new branch, put updated pair of patches there (hch has sent
> > the updated variants my way) and ask you to rebuild NFS tree. Which will
> > also suck, since it adds PITA for you and you are completely innocent in
> > that clusterfuck.
> >
> > Suggestions? I'd love to get out of that mess with minimal PITA for
> > everyone involved and minimally messed tree...
>
> Hi Al,
>
> I'd be fine with rebuilding the NFS tree. I have all the patches which
> depend on write_inode in their own separate branch anyway, so I'd only
> have to rebase that branch and then merge it with the main NFS client
> tree...
Ehh... Just after I've sent a pull request for backmerge variant...
Anyway, I've put rebased variant in the same tree, branch called
write_inode2. Same diffstat, same shortlog (sans merges). Either
branch will do; write_inode2 obviously has cleaner history.
prev parent reply other threads:[~2010-03-05 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 15:26 Merge of the 'write_inode' branch from the VFS tree Trond Myklebust
2010-03-05 15:48 ` Al Viro
2010-03-05 17:40 ` [git pull] vfs part 3 (write_inode mess) Al Viro
2010-03-08 20:22 ` Steve Dickson
2010-03-09 8:52 ` Dave Chinner
2010-03-10 23:07 ` Trond Myklebust
2010-03-05 18:02 ` Merge of the 'write_inode' branch from the VFS tree Trond Myklebust
2010-03-05 18:29 ` Al Viro [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=20100305182924.GY30031@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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