Thread (25 messages) flat view 25 messages, 2 authors, 2011-02-22

Re: [PATCH 02/14] net/fec: release mem_region requested in probe in error path and remove

From: David Miller <davem@davemloft.net>
Date: 2011-02-13 21:14:55

From: Uwe Kleine-König <redacted>
Date: Sun, 13 Feb 2011 22:07:09 +0100
Hi David,

On Fri, Feb 11, 2011 at 09:25:32PM -0800, David Miller wrote:
quoted
I can't pull from that tree because it is _NOT_ based upon net-next-2.6
and therefore brings in all kinds of commits not related to your work.
Sorry, I'm not used to the customs on netdev.  I can rebase, but still I
wonder about the reason you cannot pull for.  The only reason I can
imagine is that you fear unrelated breakage when taking these patches
that are already in Linus' tree.  But if it's that, wouldn't it be great
the realize this breakage already now and not only during the next merge
window?
My trees only merge in Linus's tree when absolutely necessary,
to resolve conflicts or similar.

We don't bring in unrelated changes into my tree, just for the
sake of doing so.

Otherwise Linus gets all of these ugly merge commits when he
pulls from me, which are entirely unnecessary.

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help