git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Prohaska <prohaska@zib.de>
To: Pierre Habouzit <madcoder@debian.org>
Cc: git@vger.kernel.org, Steffen Prohaska <prohaska@zib.de>
Subject: [PATCH] fix comment in strbuf.h to use correct name strbuf_avail()
Date: Sun,  4 Nov 2007 09:02:21 +0100	[thread overview]
Message-ID: <11941633412454-git-send-email-prohaska@zib.de> (raw)


Signed-off-by: Steffen Prohaska <prohaska@zib.de>
---
 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

             reply	other threads:[~2007-11-04  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04  8:02 Steffen Prohaska [this message]
2007-11-04  8:56 ` [PATCH] fix comment in strbuf.h to use correct name strbuf_avail() Pierre Habouzit

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=11941633412454-git-send-email-prohaska@zib.de \
    --to=prohaska@zib.de \
    --cc=git@vger.kernel.org \
    --cc=madcoder@debian.org \
    /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).