git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Guanqun Lu <guanqun.lu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] fix typo in Documentation
Date: Fri, 6 Feb 2009 14:43:58 +0100	[thread overview]
Message-ID: <237967ef0902060543q2cc13d99l852c8427fb66402b@mail.gmail.com> (raw)
In-Reply-To: <1233781241-721-1-git-send-email-guanqun.lu@gmail.com>

2009/2/4 Guanqun Lu <guanqun.lu@gmail.com>:
> Signed-off-by: Guanqun Lu <guanqun.lu@gmail.com>
> ---
>  Documentation/technical/api-strbuf.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/technical/api-strbuf.txt b/Documentation/technical/api-strbuf.txt
> index 9a4e3ea..ac56d1c 100644
> --- a/Documentation/technical/api-strbuf.txt
> +++ b/Documentation/technical/api-strbuf.txt
> @@ -21,7 +21,7 @@ allocated memory or not), use `strbuf_detach()` to unwrap a memory
>  buffer from its strbuf shell in a safe way. That is the sole supported
>  way. This will give you a malloced buffer that you can later `free()`.
>  +
> -However, it it totally safe to modify anything in the string pointed by
> +However, it is totally safe to modify anything in the string pointed by
>  the `buf` member, between the indices `0` and `len-1` (inclusive).
>
>  . The `buf` member is a byte array that has at least `len + 1` bytes

Shouldn't that be "the string pointed >>at<< by" too?

-- 
Mikael Magnusson

      parent reply	other threads:[~2009-02-06 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 21:00 [PATCH 1/2] fix typo in Documentation Guanqun Lu
2009-02-04  5:30 ` Sverre Rabbelier
2009-02-04  9:26 ` Jakub Narebski
2009-02-05  6:27   ` Guanqun Lu
2009-02-04 21:00 ` [PATCH 2/2] add test-dump-cache-tree in Makefile Guanqun Lu
2009-02-04  7:46   ` Junio C Hamano
2009-02-04  9:31   ` Jakub Narebski
2009-02-06 13:43 ` Mikael Magnusson [this message]

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=237967ef0902060543q2cc13d99l852c8427fb66402b@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=guanqun.lu@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).