Currently I maintain my own manifest repository that includes some of your stuff, and I want to keep the manifests up to date and having them in git would make it much easier. Currently their a logical merge of local_manifest.xml and default.xml. You could just start with the present files, I don't need history from before present.
Bill
On Mon, May 21, 2012 at 10:53 AM, Stephen Smalley <sds@xxxxxxxxxxxxx> wrote:
On Mon, 2012-05-21 at 10:22 -0700, William Roberts wrote:Not presently. If it would be helpful, we could set one up, but we
> Is the local_manifest file under git revision control somewhere that
> we could track from?
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
Respectfully,
William C Roberts
