From: Joshua Brindle <brindle@quarksecurity.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux-NSA <SELinux@tycho.nsa.gov>,
Daniel J Walsh <dwalsh@redhat.com>,
Eric Paris <eparis@redhat.com>,
Steve Lawrence <slawrence@tresys.com>
Subject: Re: Pruning dead/obsolete branches?
Date: Wed, 30 Oct 2013 15:00:27 -0400 [thread overview]
Message-ID: <5271574B.5050501@quarksecurity.com> (raw)
In-Reply-To: <5271566F.4070207@tycho.nsa.gov>
Stephen Smalley wrote:
> Hi,
>
> There are a number of old branches in the selinux repo that I think can
> be safely pruned, but I wanted to confirm first.
>
> The branches other than master are:
> - autotools: last attempt to convert over to using autotools. Last
> commit 2008.
>
> - integration: last attempt to integrate src-policy into master? Last
> commit 2011.
>
> - queue: Eric's branch for changes queued for merging to master, kind
> of a next branch. Last commit Feb 2013.
>
> - src-policy: source policy module work. Last commit 2010.
>
> - src-revert: Not really sure. Last commit 2011.
>
> - stable_1_0: attempt to provide a long term stable series tracking the
> 1.x versions of selinux userspace for long term distro users. Last
> commit 2008. Turned out to be pointless because the long term distros
> did their own backporting and maintenance.
>
> Any reason to retain any of these branches at this point?
Aside from queue +1 on removing all these.
For queue, I'm not sure if it is necessary or useful, I'll let Eric
chime in.
--
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 prev parent reply other threads:[~2013-10-30 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 18:56 Pruning dead/obsolete branches? Stephen Smalley
2013-10-30 19:00 ` Steve Lawrence
2013-10-30 19:00 ` Joshua Brindle [this message]
2013-10-31 15:22 ` Stephen Smalley
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=5271574B.5050501@quarksecurity.com \
--to=brindle@quarksecurity.com \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=slawrence@tresys.com \
/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.