From: Eric Paris <eparis@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jan Kara <jack@suse.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Steve French <sfrench@us.ibm.com>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: linux-next: manual merge of the ext3 tree with the cifs tree
Date: Wed, 25 Nov 2009 10:23:03 -0500 [thread overview]
Message-ID: <1259162583.4683.46.camel@dhcp231-106.rdu.redhat.com> (raw)
In-Reply-To: <20091125200444.cab8f918.sfr@canb.auug.org.au>
On Wed, 2009-11-25 at 20:04 +1100, Stephen Rothwell wrote:
> I have just noticed that I get the same conflict between the cifs tree
> and the fsnotify tree (hi Eric!) which has also included that patch from
> Christoph. Again, not a big problem.
I was doing my development against linux-next. After I posted them and
decided to commit them to my -next tree I realized they didn't commit
due to hch's patch. So I cherry picked hch's patch and decided I
wouldn't ask linus to pull until after the hch patch went in (I did it
for some things in the net-next tree as well as I recall)
What's the best way? To handle this? do you prefer to just carry the
conflict fix? should we cherry pick things and fix it ourselves? I
guess my method breaks down if the tree in question doesn't eventually
go to linus like it should.....
-Eric
next prev parent reply other threads:[~2009-11-25 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 3:06 Stephen Rothwell
2009-11-25 8:50 ` Jan Kara
2009-11-25 9:04 ` Stephen Rothwell
2009-11-25 15:23 ` Eric Paris [this message]
2010-05-12 0:13 Stephen Rothwell
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=1259162583.4683.46.camel@dhcp231-106.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sfrench@us.ibm.com \
/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
all inboxes | Powered by JetHome®