From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Jeffrey Kirsher" <jeffrey.t.kirsher@intel.com>,
"Michał Mirosław" <mirqus@gmail.com>,
"Neil Horman" <nhorman@tuxdriver.com>,
"Andy Gospodarek" <andy@greyhouse.net>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
"David Miller" <davem@davemloft.net>,
"Jay Vosburgh" <fubar@us.ibm.com>
Subject: Re: [RFC Patch] bonding: move to net/ directory
Date: Mon, 06 Jun 2011 10:20:27 -0700 [thread overview]
Message-ID: <1307380827.4994.8.camel@Joe-Laptop> (raw)
In-Reply-To: <1307379881.3098.71.camel@edumazet-laptop>
On Mon, 2011-06-06 at 19:04 +0200, Eric Dumazet wrote:
> Le lundi 06 juin 2011 à 09:50 -0700, Joe Perches a écrit :
> > There is a proposal to move some drivers/net content to
> > drivers/net/sw/
> > http://vger.kernel.org/netconf2010_slides/netconf-jtk.pdf
> > I think that'd be fine too.
> > I believe Jeff is going to submit patches soonish.
> > http://comments.gmane.org/gmane.linux.network/197232
> As long as the re-organization is done without loosing "git blame"
> information on current files, I am fine.
> If not, this is a showstopper and not worth the pain, exactly like other
> cleanup patches.
To preserve history, all of this should be done via:
git mv oldpath/file newpath/file
git commit -m newpath/file
with some extra cleanups to Kconfig/Makefile files
so no worries.
next prev parent reply other threads:[~2011-06-06 17:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 12:45 [RFC Patch] bonding: move to net/ directory Américo Wang
2011-05-23 15:13 ` Andy Gospodarek
2011-05-24 14:00 ` Américo Wang
2011-05-24 15:03 ` Andy Gospodarek
2011-05-25 12:32 ` Américo Wang
2011-05-25 15:01 ` Neil Horman
2011-05-26 9:11 ` Américo Wang
2011-05-26 13:38 ` Neil Horman
2011-05-24 16:33 ` Neil Horman
2011-05-25 12:43 ` Américo Wang
2011-05-25 15:20 ` Neil Horman
2011-05-26 9:32 ` Américo Wang
2011-05-26 13:50 ` Neil Horman
2011-05-26 14:25 ` Michał Mirosław
2011-06-06 16:34 ` Américo Wang
2011-06-06 16:50 ` Joe Perches
2011-06-06 17:04 ` Eric Dumazet
2011-06-06 17:20 ` Joe Perches [this message]
2011-06-06 17:31 ` Jeff Kirsher
2011-06-06 20:11 ` Ben Hutchings
2011-06-06 17:31 ` Jeff Kirsher
2011-06-18 2:48 ` WANG Cong
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=1307380827.4994.8.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=xiyou.wangcong@gmail.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