From: Jeremiah Mahler <jmmahler@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC v1 2/5] add strbuf_set operations documentation
Date: Mon, 9 Jun 2014 14:49:58 -0700 [thread overview]
Message-ID: <20140609214958.GA18783@hudson.localdomain> (raw)
In-Reply-To: <CAPig+cSB78YZiqWm7oTn3oFXE2yZZFbKmD6R5oHmEJMc9CtwvQ@mail.gmail.com>
Eric,
On Mon, Jun 09, 2014 at 05:53:49AM -0400, Eric Sunshine wrote:
> On Mon, Jun 9, 2014 at 4:36 AM, Jeremiah Mahler <jmmahler@gmail.com> wrote:
> > Add documentation of the strbuf_set operations to
> > technical/api-strbuf.txt.
>
> Since this patch is concise and so closely related to patch 1/5, it
> probably should be squashed into that one.
>
Fixed.
> More below.
>
> > Signed-off-by: Jeremiah Mahler <jmmahler@gmail.com>
> > ---
> > Documentation/technical/api-strbuf.txt | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/Documentation/technical/api-strbuf.txt b/Documentation/technical/api-strbuf.txt
> > index 077a709..ab430d9 100644
> > --- a/Documentation/technical/api-strbuf.txt
> > +++ b/Documentation/technical/api-strbuf.txt
> > @@ -149,6 +149,24 @@ Functions
> > than zero if the first buffer is found, respectively, to be less than,
> > to match, or be greater than the second buffer.
> >
> > +* Setting the buffer
> > +
> > +`strbuf_set`::
> > +
> > + Set the buffer to some data up to a given length.
>
> I personally find this slightly ambiguous. Upon reading it, the first
> question that pops into my mind is whether or not the existing strbuf
> content is replaced (even though "set" should imply that it is). I
> wonder if it would make sense to rewrite as:
>
> Set the buffer to [...], replacing the old content
> of the buffer.
>
> Alternately:
>
> Replace the buffer content with [...].
>
On a second reading, I agree that it is ambigous. 'Replace' is much
more clear. Great suggestion.
> Ditto for the others.
>
> > +`strbuf_setstr`::
> > +
> > + Set the buffer to a NUL-terminated string.
> > +
> > +`strbuf_setf`::
> > +
> > + Set the buffer to a formatted string.
> > +
> > +`strbuf_setbuf`::
> > +
> > + Set the current buffer to the contents of some other buffer.
> > +
> > * Adding data to the buffer
> >
> > NOTE: All of the functions in this section will grow the buffer as necessary.
> > --
--
Jeremiah Mahler
jmmahler@gmail.com
http://github.com/jmahler
next prev parent reply other threads:[~2014-06-09 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 8:36 [PATCH/RFC v1 0/5] add strbuf_set operations Jeremiah Mahler
2014-06-09 8:36 ` [PATCH/RFC v1 1/5] " Jeremiah Mahler
2014-06-09 8:36 ` [PATCH/RFC v1 2/5] add strbuf_set operations documentation Jeremiah Mahler
2014-06-09 9:53 ` Eric Sunshine
2014-06-09 21:49 ` Jeremiah Mahler [this message]
2014-06-09 8:36 ` [PATCH/RFC v1 3/5] sha1_name.c: cleanup using strbuf_set operations Jeremiah Mahler
2014-06-09 8:36 ` [PATCH/RFC v1 4/5] fast-import.c: " Jeremiah Mahler
2014-06-09 10:12 ` Eric Sunshine
2014-06-09 22:00 ` Jeremiah Mahler
2014-06-09 8:36 ` [PATCH/RFC v1 5/5] builtin/remote.c: " Jeremiah Mahler
2014-06-09 10:39 ` [PATCH/RFC v1 0/5] add " Duy Nguyen
2014-06-09 22:06 ` Jeremiah Mahler
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=20140609214958.GA18783@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).