From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: [PATCH v3 03/10] replace: factor object resolution out of replace_object
Date: Sat, 17 May 2014 14:16:32 +0200 [thread overview]
Message-ID: <20140517121640.27582.96318.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20140517120649.27582.58609.chriscool@tuxfamily.org>
From: Jeff King <peff@peff.net>
As we add new options that operate on objects before
replacing them, we'll want to be able to feed raw sha1s
straight into replace_object. Split replace_object into the
object-resolution part and the actual replacement.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
builtin/replace.c | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/builtin/replace.c b/builtin/replace.c
index 29cf699..af40129 100644
--- a/builtin/replace.c
+++ b/builtin/replace.c
@@ -123,19 +123,17 @@ static int delete_replace_ref(const char *name, const char *ref,
return 0;
}
-static int replace_object(const char *object_ref, const char *replace_ref,
- int force)
+static int replace_object_sha1(const char *object_ref,
+ unsigned char object[20],
+ const char *replace_ref,
+ unsigned char repl[20],
+ int force)
{
- unsigned char object[20], prev[20], repl[20];
+ unsigned char prev[20];
enum object_type obj_type, repl_type;
char ref[PATH_MAX];
struct ref_lock *lock;
- if (get_sha1(object_ref, object))
- die("Failed to resolve '%s' as a valid ref.", object_ref);
- if (get_sha1(replace_ref, repl))
- die("Failed to resolve '%s' as a valid ref.", replace_ref);
-
if (snprintf(ref, sizeof(ref),
"refs/replace/%s",
sha1_to_hex(object)) > sizeof(ref) - 1)
@@ -166,6 +164,18 @@ static int replace_object(const char *object_ref, const char *replace_ref,
return 0;
}
+static int replace_object(const char *object_ref, const char *replace_ref, int force)
+{
+ unsigned char object[20], repl[20];
+
+ if (get_sha1(object_ref, object))
+ die("Failed to resolve '%s' as a valid ref.", object_ref);
+ if (get_sha1(replace_ref, repl))
+ die("Failed to resolve '%s' as a valid ref.", replace_ref);
+
+ return replace_object_sha1(object_ref, object, replace_ref, repl, force);
+}
+
int cmd_replace(int argc, const char **argv, const char *prefix)
{
int force = 0;
--
1.9.rc0.17.g651113e
next prev parent reply other threads:[~2014-05-17 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 12:16 [PATCH v3 00/10] replace: add option to edit a Git object Christian Couder
2014-05-17 12:16 ` [PATCH v3 01/10] replace: refactor command-mode determination Christian Couder
2014-05-17 12:16 ` [PATCH v3 02/10] replace: use OPT_CMDMODE to handle modes Christian Couder
2014-05-17 12:16 ` Christian Couder [this message]
2014-05-17 12:16 ` [PATCH v3 04/10] replace: add --edit option Christian Couder
2014-05-17 12:16 ` [PATCH v3 05/10] replace: make sure --edit results in a different object Christian Couder
2014-05-17 12:16 ` [PATCH v3 06/10] replace: refactor checking ref validity Christian Couder
2014-05-17 12:16 ` [PATCH v3 07/10] replace: die early if replace ref already exists Christian Couder
2014-05-17 12:16 ` [PATCH v3 08/10] replace: add tests for --edit Christian Couder
2014-05-17 12:16 ` [PATCH v3 09/10] replace: add --edit to usage string Christian Couder
2014-05-17 12:16 ` [PATCH v3 10/10] Documentation: replace: describe new --edit option Christian Couder
2014-05-19 20:39 ` [PATCH v3 00/10] replace: add option to edit a Git object Junio C Hamano
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=20140517121640.27582.96318.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).