From: Pierre Habouzit <madcoder@debian.org>
To: Steffen Prohaska <prohaska@zib.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] fix comment in strbuf.h to use correct name strbuf_avail()
Date: Sun, 04 Nov 2007 09:56:51 +0100 [thread overview]
Message-ID: <20071104085651.GA26269@artemis.corp> (raw)
In-Reply-To: <11941633412454-git-send-email-prohaska@zib.de>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
On Sun, Nov 04, 2007 at 08:02:21AM +0000, Steffen Prohaska wrote:
>
> Signed-off-by: Steffen Prohaska <prohaska@zib.de>
Acked-By: Pierre Habouzit <madcoder@debian.org>
> ---
> strbuf.h | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> Note, the patch is against Junio's pu.
>
> Steffen
>
> diff --git a/strbuf.h b/strbuf.h
> index 9720826..e5cdd1e 100644
> --- a/strbuf.h
> +++ b/strbuf.h
> @@ -24,11 +24,11 @@
> *
> * strbuf_grow(sb, SOME_SIZE);
> * // ... here the memory areay starting at sb->buf, and of length
> - * // sb_avail(sb) is all yours, and you are sure that sb_avail(sb) is at
> - * // least SOME_SIZE
> + * // strbuf_avail(sb) is all yours, and you are sure that strbuf_avail(sb)
> + * // is at least SOME_SIZE
> * strbuf_setlen(sb, sb->len + SOME_OTHER_SIZE);
> *
> - * Of course, SOME_OTHER_SIZE must be smaller or equal to sb_avail(sb).
> + * Of course, SOME_OTHER_SIZE must be smaller or equal to strbuf_avail(sb).
> *
> * Doing so is safe, though if it has to be done in many places, adding the
> * missing API to the strbuf module is the way to go.
> --
> 1.5.3.4.464.ge1bc2
>
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-11-04 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 8:02 [PATCH] fix comment in strbuf.h to use correct name strbuf_avail() Steffen Prohaska
2007-11-04 8:56 ` Pierre Habouzit [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=20071104085651.GA26269@artemis.corp \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
/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).