public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:master commit in: src/libeinfo/
Date: Wed, 13 Jul 2016 22:15:55 +0000 (UTC)	[thread overview]
Message-ID: <1468447468.7f84b5d741c150cd159d5a3cda3ef532f0381826.williamh@OpenRC> (raw)

commit:     7f84b5d741c150cd159d5a3cda3ef532f0381826
Author:     Jaromil <jaromil <AT> dyne <DOT> org>
AuthorDate: Thu Jun  2 10:15:08 2016 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Wed Jul 13 22:04:28 2016 +0000
URL:        https://gitweb.gentoo.org/proj/openrc.git/commit/?id=7f84b5d7

libeinfo: document the x suffix on function names

This fixes #88.

 src/libeinfo/einfo.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/libeinfo/einfo.h b/src/libeinfo/einfo.h
index 58aedd9..83c2a79 100644
--- a/src/libeinfo/einfo.h
+++ b/src/libeinfo/einfo.h
@@ -71,6 +71,7 @@ void elog(int, const char * EINFO_RESTRICT, ...) EINFO_PRINTF(2, 3);
  *
  * The n suffix denotes that no new line should be printed.
  * The v suffix means only print if EINFO_VERBOSE is yes.
+ * The x suffix means function will exit() returning failure.
  */
 /*@{*/
 int einfon(const char * __EINFO_RESTRICT, ...) EINFO_PRINTF(1, 2);


             reply	other threads:[~2016-07-13 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 22:15 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-20 17:37 [gentoo-commits] proj/openrc:master commit in: src/libeinfo/ William Hubbs
2018-06-19 21:34 William Hubbs
2013-01-04 14:51 William Hubbs

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=1468447468.7f84b5d741c150cd159d5a3cda3ef532f0381826.williamh@OpenRC \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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