/illumos-joyent forked from illumos/illumos-gate

Community developed and maintained version of the OS/Net consolidation
  1. C 74.9%
  2. C++ 14.9%
  3. Roff 2.6%
  4. Makefile 1.8%
  5. Objective-C 1.5%
  6. Assembly 1.3%
  7. Other 3.0%
C C++ Roff Makefile Objective-C Assembly Other
Switch branches/tags
Nothing to show
Find file
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching Xcode...

If nothing happens, download Xcode and try again.

Launching Visual Studio...

If nothing happens, download the GitHub extension for Visual Studio and try again.

Pull request Compare This branch is 4350 commits ahead of illumos:master.
@jjelinek
jjelinek [illumos-gate merge] 
commit a8793c7
    9642 PKCS#11 softtoken should use explicit_bzero
Latest commit 5ea2876 Aug 2, 2018
Permalink
Failed to load latest commit information.
exception_lists [illumos-gate merge] Jul 20, 2018
usr [illumos-gate merge] Aug 2, 2018
.gitignore OS-6496 Add platform-specific topo maps for the Joyent J310x platform Dec 13, 2017
.hgtags Added tag onnv_147 for changeset 67d1861e02c15565f9bc5a6e271fa99c13d0… Aug 17, 2010
README 1126 date(1)'s usage message doesn't mention -R Sep 21, 2012
boot.manifest RELENG-608 platform boot tarball should include more grub files Apr 8, 2015
mancheck.conf OS-4220 mancheck is a flag day machine Apr 24, 2015
manifest [illumos-gate merge] Jul 31, 2018

README 

illumos gate README - Sep 16, 2012.

This is the illumos gate.  This is the illumos source tree.  It contains
the following subdirectories:

	usr/src	- 		The actual source code

	exception_lists	-	These are lists of exceptional cases
				used to limit noise during builds.
				Ideally this directory would consist of
				only empty files.

Integration Rules:

        All changes must have been reviewed, and approved by an advocate
	(below).  A code review may be performed by someone other than the
	advocate, but the final integration should still be approved by the
	advocate. 

        The advocate will want to see your webrev and hg outgoing -v.  The
	advocate will also ask about your testing, and may ask to see your
	build logs.

        All changes must adhere to typical ON style and quality rules.
        For example, pass full cstyle, applicable lint rules, etc.

        All new code must be licensed under CDDL, and modifications to existing
        code may not alter the original license terms.  Integrations of code
        from upstream sources that use another liberal open source license are
        permissible, subject to approval of the advocates or developer council.
        Exceptions to this policy shall require the approval of the developer
        council.

        Commits should have comments of the following form:

        1234 This is a sample bug report synopsis
        4567 If you have a second bug synopsis…
        Reviewed by: Frodo Baggins <frodo.baggins@underhill.net>
        Reviewed by: Legolas <elf-coder@mirkwood.org>
        Approved by: Gandalf The Grey <rti-advocate@white-council.com>

	Each commit must have at least one bug id that is listed in the
	illumos-gate project at www.illumos.org.

RTI Advocates:     advocates@lists.illumos.org
Developer Council: developer-council@lists.illumos.org

IRC channel:       #illumos on irc.freenode.net
Mailing list:      developer@lists.illumos.org