From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 3/4] replace: use argv_array in export_object
Date: Tue, 24 Jun 2014 05:46:05 -0400 [thread overview]
Message-ID: <20140624094605.GC14514@sigill.intra.peff.net> (raw)
In-Reply-To: <20140624094217.GA14216@sigill.intra.peff.net>
This is a little more verbose, but will make it easier to
make parts of our command-line conditional (without
resorting to magic numbers or lots of NULLs to get an
appropriately sized argv array).
Signed-off-by: Jeff King <peff@peff.net>
---
builtin/replace.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/builtin/replace.c b/builtin/replace.c
index eb1d2ec..2584170 100644
--- a/builtin/replace.c
+++ b/builtin/replace.c
@@ -193,15 +193,17 @@ static int replace_object(const char *object_ref, const char *replace_ref, int f
*/
static void export_object(const unsigned char *sha1, const char *filename)
{
- const char *argv[] = { "--no-replace-objects", "cat-file", "-p", NULL, NULL };
- struct child_process cmd = { argv };
+ struct child_process cmd = { NULL };
int fd;
fd = open(filename, O_WRONLY | O_CREAT | O_TRUNC, 0666);
if (fd < 0)
die_errno("unable to open %s for writing", filename);
- argv[3] = sha1_to_hex(sha1);
+ argv_array_push(&cmd.args, "--no-replace-objects");
+ argv_array_push(&cmd.args, "cat-file");
+ argv_array_push(&cmd.args, "-p");
+ argv_array_push(&cmd.args, sha1_to_hex(sha1));
cmd.git_cmd = 1;
cmd.out = fd;
--
2.0.0.566.gfe3e6b2
next prev parent reply other threads:[~2014-06-24 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 9:42 [PATCH 0/4] git replace --edit --raw Jeff King
2014-06-24 9:43 ` [PATCH 1/4] replace: replace spaces with tabs in indentation Jeff King
2014-06-24 9:45 ` [PATCH 2/4] avoid double close of descriptors handed to run_command Jeff King
2014-06-24 9:46 ` Jeff King [this message]
2014-06-24 9:46 ` [PATCH 4/4] replace: add a --raw mode for --edit Jeff King
2014-06-25 1:40 ` Eric Sunshine
2014-06-25 10:24 ` Jeff King
2014-06-25 22:33 ` Junio C Hamano
2014-06-26 15:55 ` Jeff King
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=20140624094605.GC14514@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.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).