util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 1/4] docs: mention Open Group requirements
Date: Sun, 25 Nov 2012 12:01:08 +0000	[thread overview]
Message-ID: <1353844871-6047-2-git-send-email-kerolasa@iki.fi> (raw)
In-Reply-To: <1353844871-6047-1-git-send-email-kerolasa@iki.fi>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1355 bytes --]

Commands cal col ipcrm ipcs kill line logger mesg more newgrp pg renice
has Open Group requirements.  Contributors need to be aware of them.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---
 Documentation/howto-contribute.txt | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/Documentation/howto-contribute.txt b/Documentation/howto-contribute.txt
index 5df6389..e0f8ad7 100644
--- a/Documentation/howto-contribute.txt
+++ b/Documentation/howto-contribute.txt
@@ -117,6 +117,35 @@ Various notes
 	  multiple lines. In case the shorthand does not look good on one
 	  line use normal "if () else" syntax.
 
+Standards compliancy
+
+	Some of the commands maintained in this package has Open Group
+	requirements. These commands are;
+
+		cal
+		col
+		ipcrm
+		ipcs
+		kill
+		line
+		logger
+		mesg
+		more
+		newgrp
+		pg
+		renice
+
+	If you change these tools please make sure a change does not
+	conflict with the latest standard.  For example it is
+	recommendable not to add short command line options before they
+	are part of standard.  Introducing new short options is
+	acceptable.
+
+		The Single UNIX® Specification, Version 2
+		Copyright © 1997 The Open Group
+
+		http://pubs.opengroup.org/onlinepubs/7908799/xcuix.html
+
 IRC channel
 
 	* We have a new #util-linux IRC channel at freenode.net.
-- 
1.8.0


  reply	other threads:[~2012-11-25 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 12:01 [PATCH 0/4] pull: subsequent patches are also available from my git Sami Kerola
2012-11-25 12:01 ` Sami Kerola [this message]
2012-11-25 13:42   ` [PATCH 1/4] docs: mention Open Group requirements Adam Sampson
2012-11-25 18:43     ` Sami Kerola
     [not found]   ` <50B261D9.3080403@gmail.com>
2012-11-25 18:47     ` Sami Kerola
     [not found]   ` <50B28EF3.2070708@zoho.com>
2012-11-25 22:57     ` Sami Kerola
2012-11-25 12:01 ` [PATCH 2/4] docs: remove dead link Sami Kerola
2012-11-25 12:01 ` [PATCH 3/4] docs: mention what Open Group has marked legacy Sami Kerola
2012-11-25 12:01 ` [PATCH 4/4] docs: ddate removal Sami Kerola
2012-11-30 12:44 ` [PATCH 0/4] pull: subsequent patches are also available from my git Karel Zak

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=1353844871-6047-2-git-send-email-kerolasa@iki.fi \
    --to=kerolasa@iki.fi \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).