All of lore.kernel.org
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Git Mailing List <git@vger.kernel.org>,
	Pierre Habouzit <madcoder@debian.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH 2/3] add strbuf_adddup()
Date: Sat, 10 Nov 2007 12:16:05 +0100	[thread overview]
Message-ID: <473592F5.2070407@lsrfire.ath.cx> (raw)
In-Reply-To: <20071110004635.GA14992@sigill.intra.peff.net>

Add a new function, strbuf_adddup(), that appends a duplicate of a
part of a struct strbuf to end of the latter.

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
---
 strbuf.c |    7 +++++++
 strbuf.h |    1 +
 2 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/strbuf.c b/strbuf.c
index 536b432..dbd8c4b 100644
--- a/strbuf.c
+++ b/strbuf.c
@@ -106,6 +106,13 @@ void strbuf_add(struct strbuf *sb, const void *data, size_t len)
 	strbuf_setlen(sb, sb->len + len);
 }
 
+void strbuf_adddup(struct strbuf *sb, size_t pos, size_t len)
+{
+	strbuf_grow(sb, len);
+	memcpy(sb->buf + sb->len, sb->buf + pos, len);
+	strbuf_setlen(sb, sb->len + len);
+}
+
 void strbuf_addf(struct strbuf *sb, const char *fmt, ...)
 {
 	int len;
diff --git a/strbuf.h b/strbuf.h
index 21d8944..1391912 100644
--- a/strbuf.h
+++ b/strbuf.h
@@ -101,6 +101,7 @@ static inline void strbuf_addstr(struct strbuf *sb, const char *s) {
 static inline void strbuf_addbuf(struct strbuf *sb, struct strbuf *sb2) {
 	strbuf_add(sb, sb2->buf, sb2->len);
 }
+extern void strbuf_adddup(struct strbuf *sb, size_t pos, size_t len);
 
 typedef void (*expand_fn_t) (struct strbuf *sb, const char *placeholder, void *context);
 extern void strbuf_expand(struct strbuf *sb, const char *format, const char **placeholders, expand_fn_t fn, void *context);
-- 
1.5.3.5.1651.g30bf

  parent reply	other threads:[~2007-11-10 11:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09  0:49 [PATCH 2/2] --pretty=format: on-demand format expansion René Scharfe
2007-11-09  1:24 ` Johannes Schindelin
2007-11-09 21:13   ` René Scharfe
2007-11-09 22:18     ` Johannes Schindelin
2007-11-09 22:30       ` Junio C Hamano
2007-11-09  4:50 ` Jeff King
2007-11-09 23:16   ` René Scharfe
2007-11-10  0:31     ` Johannes Schindelin
2007-11-10  0:49       ` Jeff King
2007-11-10  0:46     ` Jeff King
2007-11-10 11:12       ` René Scharfe
2007-11-10 16:07         ` Johannes Schindelin
2007-11-10 16:24           ` René Scharfe
2007-11-10 20:36           ` Jeff King
2007-11-10 20:34         ` Jeff King
2007-11-11  8:13           ` Jeff King
2007-11-10 11:14       ` [PATCH 1/3] --pretty=format: parse commit message only once René Scharfe
2007-11-10 11:16       ` René Scharfe [this message]
2007-11-10 11:18       ` [PATCH 3/3] --format=pretty: avoid calculating expensive expansions twice René Scharfe
2007-11-11 10:29         ` Junio C Hamano
2007-11-09  4:52 ` [PATCH 2/2] --pretty=format: on-demand format expansion Jeff King
2007-11-09 23:20   ` René Scharfe
2007-11-10  0:51     ` Jeff King
2007-11-09 23:39 ` Paul Mackerras

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=473592F5.2070407@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=madcoder@debian.org \
    --cc=paulus@samba.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.