From: Stephen Smalley <sds@tycho.nsa.gov>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: selinux@tycho.nsa.gov, seandroid@tycho.nsa.gov
Subject: Re: local_mainfest.xml
Date: Mon, 21 May 2012 13:53:48 -0400 [thread overview]
Message-ID: <1337622828.28413.106.camel@moss-pluto> (raw)
In-Reply-To: <CAFftDdp7eW0swem7kMD589eQm6LT4pN5yf4-at9wMv1T9wY9rQ@mail.gmail.com>
On Mon, 2012-05-21 at 10:22 -0700, William Roberts wrote:
> Is the local_manifest file under git revision control somewhere that
> we could track from?
Not presently. If it would be helpful, we could set one up, but we
should make sure we work out how it should be organized up front. At
present, we provide 6 versions of the local_manifest.xml file. There
are three baselines (master, 4.0.3, 4.0.4) and two fetch URLs (one
git-based and one http-based). The repo could contain two files
(local_manifest.xml and local_manifest_http.xml) with three branches
(master, seandroid-4.0.3, seandroid-4.0.4), thereby mirroring the
structure of the other git projects. Is that what you would want? Did
you need/want any of the older versions of the files included in the
history (if so, which ones?) or just start from the current ones?
--
Stephen Smalley
National Security Agency
--
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:[~2012-05-21 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 17:22 local_mainfest.xml William Roberts
2012-05-21 17:53 ` Stephen Smalley [this message]
2012-05-21 18:17 ` local_mainfest.xml Radzykewycz, T (Radzy)
2012-05-21 20:32 ` local_mainfest.xml Stephen Smalley
2012-05-29 20:01 ` local_mainfest.xml Stephen Smalley
2012-05-21 19:05 ` local_mainfest.xml William Roberts
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=1337622828.28413.106.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=bill.c.roberts@gmail.com \
--cc=seandroid@tycho.nsa.gov \
--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.