From: Joshua Brindle <method@manicmethod.com>
To: SE Linux <selinux@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Subject: [ANN] SELinux userland repository, wiki and bug tracking on oss.tresys.com
Date: Fri, 15 Aug 2008 13:50:42 -0400 [thread overview]
Message-ID: <48A5C1F2.3080002@manicmethod.com> (raw)
We have finished migrating the SELinux userland repository and bug tracking, it is available at http://oss.tresys.com/projects/selinux.
The source code repository for read access is available via git:
git clone http://oss.tresys.com/git/selinux.git
or you can browse the source via:
http://oss.tresys.com/projects/selinux/browser
All users following trunk should switch over to git, subversion access on sourceforge will be turned off in the near future.
Anyone who wants to follow commits to the git repo are encouraged to add themselves to the selinux-commit mailing list by going to http://oss.tresys.com/mailman/listinfo/selinux-commits.
The page is a trac wiki so anyone interested in updating or writing new pages for the site can make an account and request access to modify.
In addition to moving to a more modern SCM and having more control over the content this move also provides additional resources to SELinux developers.
Please let me know if there are any questions concerning this migration.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2008-08-15 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 17:50 Joshua Brindle [this message]
2008-08-20 22:57 ` [ANN] SELinux userland repository, wiki and bug tracking on oss.tresys.com Joshua Brindle
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=48A5C1F2.3080002@manicmethod.com \
--to=method@manicmethod.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.