From: Russell Coker <russell@coker.com.au>
To: selinux@tycho.nsa.gov
Cc: Refpolicy Mail List <refpolicy@oss1.tresys.com>
Subject: Re: ANN: Reference Policy moved to GitHub
Date: Sat, 14 Jun 2014 11:46:43 +1000 [thread overview]
Message-ID: <1766633.zdlLJ7D5UV@xev> (raw)
In-Reply-To: <5395CAA0.4010900@tresys.com>
On Mon, 9 Jun 2014 10:54:24 Christopher J. PeBenito wrote:
> Since open source development workflows have moved towards services like
> GitHub and Bitbucket, we have decided to move Reference Policy's
> repositories to GitHub. The project wiki is now available here:
http://www.cultureoffset.org/
Are you sure that GitHub is a good choice?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
WARNING: multiple messages have this Message-ID (diff)
From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ANN: Reference Policy moved to GitHub
Date: Sat, 14 Jun 2014 11:46:43 +1000 [thread overview]
Message-ID: <1766633.zdlLJ7D5UV@xev> (raw)
In-Reply-To: <5395CAA0.4010900@tresys.com>
On Mon, 9 Jun 2014 10:54:24 Christopher J. PeBenito wrote:
> Since open source development workflows have moved towards services like
> GitHub and Bitbucket, we have decided to move Reference Policy's
> repositories to GitHub. The project wiki is now available here:
http://www.cultureoffset.org/
Are you sure that GitHub is a good choice?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-06-14 1:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:54 ANN: Reference Policy moved to GitHub Christopher J. PeBenito
2014-06-09 14:54 ` [refpolicy] " Christopher J. PeBenito
2014-06-14 1:46 ` Russell Coker [this message]
2014-06-14 1:46 ` Russell Coker
2014-06-14 7:20 ` Elia Pinto
2014-06-14 7:20 ` Elia Pinto
2014-06-14 14:43 ` Russell Coker
2014-06-14 14:43 ` Russell Coker
2014-06-26 20:07 ` Luis Ressel
2014-06-27 14:45 ` Christopher J. PeBenito
2014-06-27 17:56 ` Luis Ressel
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=1766633.zdlLJ7D5UV@xev \
--to=russell@coker.com.au \
--cc=refpolicy@oss1.tresys.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.