linux-kernel - Re: linux-next: manual merge of the vfs tree with the v9fs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 7 Jan 2012 17:44:34 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Eric Van Hensbergen <ericvh@...il.com>
Cc:	Al Viro <viro@...iv.linux.org.uk>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>
Subject: Re: linux-next: manual merge of the vfs tree with the v9fs tree

Hi Eric,

On Fri, 6 Jan 2012 22:38:57 -0600 Eric Van Hensbergen <ericvh@...il.com> wrote:
>
> What's typically the right process for me to prep the merge for Linus?
> Should I pull Al's patchset and then apply mine on top of it so I can
> merge your merge fix or just have my for-linus tree based on his
> current working merge (which I assume has Al's by now).  Just a bit
> confused because rebasing was discouraged last merge window -- but not
> sure how to deal with the conflict without a rebase....

Just warn Linus that there will be a conflict with Al's stuff.  You could
supply him with the patch I gave you just for good measure, but he is
good (better then me) at fixing merge conflicts and will ping you if he
has doubts.

i.e. don't rebase or even bother doing the merge yourself.  Just ask him
to pull what was in linux-next.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped