PERFORCE change 92056 for review
dingo at microbsd.net
Mon Feb 20 12:46:27 PST 2006
> FYI, all the other TrustedBSD branches use 'trustedbsd_' as a prefix of their
> branch name:
> If you were following that pattern you would use 'trustedbsd_sebsd2' rather
> than just 'sebsd2'. Also, all the other TrustedBSD branches are branched
> from the 'trustedbsd' base branch in //depot/projects/trustedbsd/base/...
> For example, the audit3 branch's view is:
> //depot/projects/trustedbsd/base/... //depot/projects/trustedbsd/audit3/...
> Wherease the sebsd2 branch's view is:
> //depot/vendor/freebsd/src/... //depot/projects/trustedbsd/sebsd2/...
> Is the inconsistency intentional?
the trustedbsd_ branch name was an over sight, the branching
from //depot/vendor/freebsd/src/... instead
of //depot/projects/trustedbsd/base/... was due to a conversation
pertaining to pulling in audit to sebsd2 while working to bring it
current, referring to the specific email would be
Re: Migrating SeBSD to CUREENT - Are
we alive ???
Thu, 16 Feb 2006 13:45:11 +0000
(GMT) (21:45 PHT)
where Robert stated it would be best to branch from vendor/freebsd or
even trustedbsd/mac to include the audit code, though mac is in an
untested state. So i went with vendor/src/... now as for the branch
name, how can we resolv that.
More information about the p4-projects