From: Johannes Sixt <j6t@kdbg•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org, Johannes Sixt <j6t@kdbg•org>
Subject: [PATCH 0/3] Miscellanous cleanups around start_command/run_command callers
Date: Mon, 8 Jun 2009 22:34:28 +0200 [thread overview]
Message-ID: <cover.1244492658.git.j6t@kdbg.org> (raw)
This is just to flush a queue of unrelated changes before they pile up.
I found these while I reviewed start_command and run_command call sites.
Johannes Sixt (3):
Simplify some instances of run_command() by using
run_command_v_opt().
diff.c: plug a memory leak in an error path
Simplify some 'fprintf(stderr); return -1;' by using 'return error()'
builtin-help.c | 16 ++++++----------
builtin-receive-pack.c | 10 +++-------
diff.c | 1 +
ll-merge.c | 11 ++---------
merge-index.c | 42 +++++++++++++-----------------------------
5 files changed, 25 insertions(+), 55 deletions(-)
next reply other threads:[~2009-06-08 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 20:34 Johannes Sixt [this message]
2009-06-08 20:34 ` [PATCH 1/3] Simplify some instances of run_command() by using run_command_v_opt() Johannes Sixt
2009-06-08 20:34 ` [PATCH 2/3] diff.c: plug a memory leak in an error path Johannes Sixt
2009-06-08 20:34 ` [PATCH 3/3] Simplify some 'fprintf(stderr); return -1;' by using 'return error()' Johannes Sixt
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=cover.1244492658.git.j6t@kdbg.org \
--to=j6t@kdbg$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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