From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/8] Use a clearer style to issue commands to remote helpers
Date: Sun, 9 Aug 2009 22:17:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0908092211030.8306@pacific.mpi-cbg.de> (raw)
In-Reply-To: <alpine.LNX.2.00.0908091526350.27553@iabervon.org>
Hi,
On Sun, 9 Aug 2009, Daniel Barkalow wrote:
> This style is overkill for some commands, but it's worthwhile to use
> the same style to issue all commands, and it's useful to avoid
> open-coding string lengths.
>
> Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
> ---
Thanks. I am positively surprised that you did this patch in spite of the
basis already being in 'next'.
> + strbuf_addstr(&buf, "capabilities\n");
> + write_in_full(helper->in, buf.buf, buf.len);
> + strbuf_reset(&buf);
Hmm. I think you use the same paradigm three times. Maybe it is time to
heed the DRY principle and introduce a helper function?
Maybe something like
void fprintf_in_full(struct strbuf *buf, int fd, const char *format, ...)
{
va_list ap;
va_start(ap, format);
strbuf_reset(buf);
strbuf_vaddf(buf, format, ap);
write_in_full(fd, buf->buf, buf->len);
va_end(ap);
}
But I keep forgetting that there is no strbuf_vaddf() in 'next'... maybe
it is high time that I forget my promise and re-submit that series?
Ciao,
Dscho
next prev parent reply other threads:[~2009-08-09 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 19:28 [PATCH 1/8] Use a clearer style to issue commands to remote helpers Daniel Barkalow
2009-08-09 20:17 ` Johannes Schindelin [this message]
2009-08-09 21:14 ` Daniel Barkalow
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=alpine.DEB.1.00.0908092211030.8306@pacific.mpi-cbg.de \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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