From: David Miller <davem@davemloft•net>
To: sfr@canb•auug.org.au
Cc: paul.moore@hp•com, jmorris@namei•org, akpm@linux-foundation•org,
linux-next@vger•kernel.org
Subject: Re: Labeled Networking tree for linux-next
Date: Wed, 23 Jul 2008 19:53:26 -0700 (PDT) [thread overview]
Message-ID: <20080723.195326.79993514.davem@davemloft.net> (raw)
In-Reply-To: <20080724100624.6c6127ed.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 24 Jul 2008 10:06:24 +1000
> I have no problem with trees coming into linux-next from more than one
> source (see e.g. the wireless tree which is merged into the net tree).
> In fact it can be useful so that you will discover conflicting changes in
> the security and net trees before you have your tree merged into theirs.
Yes, indeed, this would work from my side as well. The wireless
model has worked well so far.
next prev parent reply other threads:[~2008-07-24 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:44 Labeled Networking tree for linux-next Paul Moore
2008-07-23 18:16 ` James Morris
2008-07-23 20:19 ` Paul Moore
2008-07-24 0:06 ` Stephen Rothwell
2008-07-24 2:53 ` David Miller [this message]
2008-07-24 13:47 ` Paul Moore
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=20080723.195326.79993514.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=akpm@linux-foundation$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.moore@hp$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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