From: Thiago Farina <tfransosi@gmail.com>
To: git@vger.kernel.org
Cc: jrnieder@gmail.com
Subject: [PATCH] Documentation: document the string-list macros.
Date: Sun, 5 Sep 2010 14:51:17 -0300 [thread overview]
Message-ID: <1283709077-5438-1-git-send-email-tfransosi@gmail.com> (raw)
Add basic documentation about the string-list.h macros
that can be used to initialize the string_list structure.
Signed-off-by: Thiago Farina <tfransosi@gmail.com>
---
Documentation/technical/api-string-list.txt | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/Documentation/technical/api-string-list.txt b/Documentation/technical/api-string-list.txt
index 3f575bd..cec11b5 100644
--- a/Documentation/technical/api-string-list.txt
+++ b/Documentation/technical/api-string-list.txt
@@ -52,6 +52,18 @@ However, if you use the list to check if a certain string was added
already, you should not do that (using unsorted_string_list_has_string()),
because the complexity would be quadratic again (but with a worse factor).
+Macros
+------
+
+`STRING_LIST_INIT_NODUP`::
+
+ Initialize the members and set the `strdup_strings` member to 0.
+
+`STRING_LIST_INIT_DUP`::
+
+ Initialize the members and set the `strdup_strings` member to 1.
+
+
Functions
---------
--
1.7.2.3.313.gcd15
next reply other threads:[~2010-09-05 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 17:51 Thiago Farina [this message]
2010-09-05 20:03 ` [demo/patch 0/3] Re: [PATCH] Documentation: document the string-list macros Jonathan Nieder
2010-09-05 20:04 ` [demo/PATCH 1/3] string-list: introduce string_list_init() Jonathan Nieder
2010-09-05 20:06 ` [demo/PATCH 1/3] string-list: Document STRING_LIST_INIT_* and string_list_init() Jonathan Nieder
2010-09-05 20:08 ` [demo/PATCH 3/3] Make initialization of string_lists more consistent Jonathan Nieder
2010-09-05 23:19 ` [demo/patch 0/3] Re: [PATCH] Documentation: document the string-list macros Thiago Farina
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=1283709077-5438-1-git-send-email-tfransosi@gmail.com \
--to=tfransosi@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).