From 8831110100e6e3941e27067514a857534c52962f Mon Sep 17 00:00:00 2001 From: Cyrill Gorcunov Date: Sun, 16 Oct 2011 15:40:12 +0400 Subject: [PATCH] Add "patches" page Signed-off-by: Cyrill Gorcunov --- css/base.css | 53 +++++++------------------------------- navbar.inc | 1 + patches.php | 83 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 93 insertions(+), 44 deletions(-) create mode 100644 patches.php diff --git a/css/base.css b/css/base.css index 73bde0c1..ba7b9cf8 100644 --- a/css/base.css +++ b/css/base.css @@ -11,6 +11,7 @@ body { background-color: #4682b4; font-size: 16px; } + img { border: none; } @@ -142,47 +143,11 @@ p { line-height: 24px; } -/* -4682B4 -4682B4 - -496B87 -496B87 - -174A75 -174A75 - -76ACDA -76ACDA - -90B8DA -90B8DA -FFD658 -FFD658 - -BFA861 -BFA861 - -A6841D -A6841D - -FFE082 -FFE082 - -FFE8A3 -FFE8A3 -FF8A58 -FF8A58 - -BF7D61 -BF7D61 - -A6451D -A6451D - -FFA782 -FFA782 - -FFBEA3 -FFBEA3 -*/ +.code { + margin-left: 30px; + margin-bottom: -10px; + padding: 2px; + color: #000; + background-color: #f9f9f9; + font-family: Monospace; +} diff --git a/navbar.inc b/navbar.inc index d88baf4a..22740dcd 100644 --- a/navbar.inc +++ b/navbar.inc @@ -13,6 +13,7 @@ require('./version.inc');
  • Git-Repo
  • Docs
  • Bugs
    • +
  • Patches
  • Links
  • Credits
    • diff --git a/patches.php b/patches.php new file mode 100644 index 00000000..df9ccfbc --- /dev/null +++ b/patches.php @@ -0,0 +1,83 @@ + + + + + + + + + The Netwide Assembler: NASM + + + + + + +
    +
    + +

    Patches for the NASM

    +

    The NASM uses the GIT version control system. + So we prefer to obtain well formatted patches which would be simply merged into the + repo without much efforts.

    + +

    Signing your work

    + +

    To improve tracking of who did what we've introduced a "sign-off" procedure + on patches that are being emailed around.

    + +

    The sign-off is a simple line at the end of the explanation for the + patch, which certifies that you wrote it or otherwise have the right to + pass it on as a open-source patch. The rules are pretty simple - if you + can certify the below...

    + +

    Developer's Certificate of Origin 1.1

    + +

    By making a contribution to this project, I certify that:

    + +

    (a) The contribution was created in whole or in part by me and I + have the right to submit it under the open source license + indicated in the file; or

    + +

    (b) The contribution is based upon previous work that, to the best + of my knowledge, is covered under an appropriate open source + license and I have the right under that license to submit that + work with modifications, whether created in whole or in part + by me, under the same open source license (unless I am + permitted to submit under a different license), as indicated + in the file; or

    + +

    (c) The contribution was provided directly to me by some other + person who certified (a), (b) or (c) and I have not modified + it.

    + +

    (d) I understand and agree that this project and the contribution + are public and that a record of the contribution (including all + personal information I submit with it, including my sign-off) is + maintained indefinitely and may be redistributed consistent with + this project or the open source license(s) involved.

    + +

    then you just add a line saying

    + +

    Signed-off-by: Random J Developer + <random@developer.example.org>

    + +

    using your real name (please, no pseudonyms or anonymous contributions if + possible).

    + +

    Example of a patch message

    + +

    +

    + From: Random J Developer <random@developer.example.org>
    + Subject: [PATCH] Short patch description

    + + Long patch description (could be skipped if the patch
    + is trivial enough)

    + + Signed-off-by: Random J Developer <random@developer.example.org> +

    +
    +
    + + -- 2.11.4.GIT