netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Cc: Hans Schillstrom <hans@schillstrom.com>,
	Julian Anastasov <ja@ssi.bg>,
	Wensong Zhang <wensong@linux-vs.org>,
	Patrick McHardy <kaber@trash.net>,
	David Miller <davem@davemloft.net>
Subject: [Announce] New IPVS GIT trees
Date: Tue, 5 Apr 2011 09:24:17 +0900	[thread overview]
Message-ID: <20110405002416.GE16175@verge.net.au> (raw)

Hi,

I would like to announce that I have created two new trees
to help me maintain the flow of changes to IPVS.

1) ipvs-2.6

   This the master branch of tree is based of the master
   branch of Patrick's nf-2.6 tree. Patches to rc kernels
   should be made against the master branch. That is, bug fixes.

   I intend to add some other branches for backports and the like.
   Temporary branches, such as for-patrick, will come and
   go as the need arises.

   git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-2.6.git

2) ipvs-next-2.6

   This the master branch of tree is based of the master
   branch of Patrick's nf-next-2.6 tree. Patches for the next/current
   merge window should be made against the master branch.
   This is where the development of new features should be done.

   My intention is to close this tree to new features during the merge window.

   I may add topic branches as the need arises.
   Temporary branches, such as for-patrick, will come and
   go as the need arises.

   git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next-2.6.git

My lvs-test-2.6 tree is now deprecated.  Please avoid using it if possible.
I intend to delete it in the not to distant future.

                 reply	other threads:[~2011-04-05  0:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110405002416.GE16175@verge.net.au \
    --to=horms@verge.net.au \
    --cc=davem@davemloft.net \
    --cc=hans@schillstrom.com \
    --cc=ja@ssi.bg \
    --cc=kaber@trash.net \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=wensong@linux-vs.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;
as well as URLs for NNTP newsgroup(s).