From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: + git-net-git-rejects.patch added to -mm tree
Date: Mon, 05 May 2008 14:04:50 -0700 (PDT) [thread overview]
Message-ID: <20080505.140450.48875249.davem@davemloft.net> (raw)
In-Reply-To: <20080505130911.52b22577.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Mon, 5 May 2008 13:09:11 -0700
> I noticed that there were rather a lot of changes in
> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
> which are not in linux-next, perhaps due to time lag.
Andrew, I think you simply have to "let go" of one side or
the other.
If you're going to base on top of linux-next, then let it run
it's course and don't try to suck in the GIT trees on top
of that which linux-next takes already.
next prev parent reply other threads:[~2008-05-05 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200805051905.m45J5eG7032280@imap1.linux-foundation.org>
2008-05-05 19:51 ` + git-net-git-rejects.patch added to -mm tree David Miller
2008-05-05 20:09 ` Andrew Morton
2008-05-05 21:04 ` David Miller [this message]
2008-05-05 21:18 ` Andrew Morton
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=20080505.140450.48875249.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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