From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
Denis Lunev <den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Alexey Dobriyan
<adobriyan-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: net namespaces git repo
Date: Fri, 09 Nov 2007 14:06:53 +0300 [thread overview]
Message-ID: <47343F4D.2050501@openvz.org> (raw)
Hi, guys!
We have uploaded the git repo at git.openvz.org:
http://git.openvz.org/?p=linux-2.6-netns;a=summary
You may setup a remote repo on it and fetch it from time to time.
git daemon seems to work on it :) so fetch commits via git protocol.
I will try not to forget to inform everybody who is interested
in it about major events (rebase/new subsystems). If the
development will be very active, I think it would make sense to
setup a separate mailing list for it.
There are 3 branches in it:
1. master - this is the Linus' tree. Most likely we'll not update it :);
2. net-2.6 - this is a David Miller's netdev tree. We are going to
fetch it from time to time (I plan once a week at least) and rebase
the netns patches on it;
3. net-2/6-netns - this is going to be our main development branch.
Currently there are only unix and packet sockets virtualized. This is
the part which looks complete by now. I hope that we'll manage to
get IPv4 there next week.
Hope to see IPv6 patches from you soon. Happy hacking!
Thanks,
Pavel
next reply other threads:[~2007-11-09 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 11:06 Pavel Emelyanov [this message]
[not found] ` <47343F4D.2050501-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-09 11:15 ` net namespaces git repo Daniel Lezcano
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=47343F4D.2050501@openvz.org \
--to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=adobriyan-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.