git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH v2 2/6] string_list: add two new functions for splitting strings
Date: Wed, 12 Sep 2012 10:55:25 -0700	[thread overview]
Message-ID: <7vtxv3ceia.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <50508A44.1020008@alum.mit.edu> (Michael Haggerty's message of "Wed, 12 Sep 2012 15:12:36 +0200")

Michael Haggerty <mhagger@alum.mit.edu> writes:

> On 09/11/2012 12:33 AM, Junio C Hamano wrote:
>> Michael Haggerty <mhagger@alum.mit.edu> writes:
>> 
>>> +`string_list_split`, `string_list_split_in_place`::
>>> +
>>> +	Split a string into substrings on a delimiter character and
>>> +	append the substrings to a `string_list`.  If `maxsplit` is
>>> +	non-negative, then split at most `maxsplit` times.  Return the
>>> +	number of substrings appended to the list.
>> 
>> 
>> I recall that we favor
>> 
>> `A`::
>> `B`::
>> 
>> 	Description for A and B
>> 
>> for some reason but do not remember exactly why.
>
> Will change.  Thanks.

Thanks.  It comes from this one:

commit bf474e2402e51843e8230c064da6ccfdf3a8ff54
Author: Markus Heidelberg <markus.heidelberg@web.de>
Date:   Fri Jan 16 22:42:33 2009 +0100

    Documentation: let asciidoc align related options
    
    Command line options can share the same paragraph of description, if
    they are related or synonymous. In these cases they should be
    written among each other, so that asciidoc can format them itself.
    
    Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>

  reply	other threads:[~2012-09-12 17:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 21:18 [PATCH v2 0/6] Add some string_list-related functions Michael Haggerty
2012-09-10 21:18 ` [PATCH v2 1/6] string_list: add function string_list_append_nodup() Michael Haggerty
2012-09-10 21:56   ` Junio C Hamano
2012-09-10 22:03     ` Michael Haggerty
2012-09-12 13:32     ` Michael Haggerty
2012-09-10 21:18 ` [PATCH v2 2/6] string_list: add two new functions for splitting strings Michael Haggerty
2012-09-10 22:00   ` Junio C Hamano
2012-09-10 22:33   ` Junio C Hamano
2012-09-12 13:12     ` Michael Haggerty
2012-09-12 17:55       ` Junio C Hamano [this message]
2012-09-10 21:18 ` [PATCH v2 3/6] string_list: add a new function, filter_string_list() Michael Haggerty
2012-09-10 21:18 ` [PATCH v2 4/6] string_list: add a new function, string_list_remove_duplicates() Michael Haggerty
2012-09-10 21:18 ` [PATCH v2 5/6] string_list: add a function string_list_longest_prefix() Michael Haggerty
2012-09-10 21:18 ` [PATCH v2 6/6] api-string-list.txt: initialize the string_list the easy way Michael Haggerty

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=7vtxv3ceia.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    /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).