From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Joey Hess <joey@kitenet.net>
Subject: [PATCH v2 06/10] sha1_file: perform object replacement in sha1_object_info_extended()
Date: Sat, 07 Dec 2013 17:21:01 +0100 [thread overview]
Message-ID: <20131207162106.21478.38769.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20131207160514.21478.72966.chriscool@tuxfamily.org>
sha1_object_info_extended() should perform object replacement
if it is needed.
The simplest way to do that is to make it call
lookup_replace_object_extended().
And now its "unsigned flags" parameter is used as it is passed
to lookup_replace_object_extended().
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
sha1_file.c | 13 +++++++------
t/t6050-replace.sh | 2 +-
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 482037e..ee224e4 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -2448,8 +2448,9 @@ int sha1_object_info_extended(const unsigned char *sha1, struct object_info *oi,
struct cached_object *co;
struct pack_entry e;
int rtype;
+ const unsigned char *real = lookup_replace_object_extended(sha1, flags);
- co = find_cached_object(sha1);
+ co = find_cached_object(real);
if (co) {
if (oi->typep)
*(oi->typep) = co->type;
@@ -2461,23 +2462,23 @@ int sha1_object_info_extended(const unsigned char *sha1, struct object_info *oi,
return 0;
}
- if (!find_pack_entry(sha1, &e)) {
+ if (!find_pack_entry(real, &e)) {
/* Most likely it's a loose object. */
- if (!sha1_loose_object_info(sha1, oi)) {
+ if (!sha1_loose_object_info(real, oi)) {
oi->whence = OI_LOOSE;
return 0;
}
/* Not a loose object; someone else may have just packed it. */
reprepare_packed_git();
- if (!find_pack_entry(sha1, &e))
+ if (!find_pack_entry(real, &e))
return -1;
}
rtype = packed_object_info(e.p, e.offset, oi);
if (rtype < 0) {
- mark_bad_packed_object(e.p, sha1);
- return sha1_object_info_extended(sha1, oi, 0);
+ mark_bad_packed_object(e.p, real);
+ return sha1_object_info_extended(real, oi, 0);
} else if (in_delta_base_cache(e.p, e.offset)) {
oi->whence = OI_DBCACHED;
} else {
diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
index b90dbdc..bb785ec 100755
--- a/t/t6050-replace.sh
+++ b/t/t6050-replace.sh
@@ -276,7 +276,7 @@ test_expect_success '-f option bypasses the type check' '
git replace -f HEAD^ $BLOB
'
-test_expect_failure 'git cat-file --batch works on replace objects' '
+test_expect_success 'git cat-file --batch works on replace objects' '
git replace | grep $PARA3 &&
echo $PARA3 | git cat-file --batch
'
--
1.8.5.1.102.g090758b
next prev parent reply other threads:[~2013-12-07 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 16:20 [PATCH v2 00/10] teach replace objects to sha1_object_info_extended() Christian Couder
2013-12-07 16:20 ` [PATCH v2 01/10] Rename READ_SHA1_FILE_REPLACE flag to LOOKUP_REPLACE_OBJECT Christian Couder
2013-12-07 16:20 ` [PATCH v2 02/10] replace_object: don't check read_replace_refs twice Christian Couder
2013-12-07 16:20 ` [PATCH v2 03/10] Introduce lookup_replace_object_extended() to pass flags Christian Couder
2013-12-07 16:20 ` [PATCH v2 04/10] Add an "unsigned flags" parameter to sha1_object_info_extended() Christian Couder
2013-12-07 16:21 ` [PATCH v2 05/10] t6050: show that git cat-file --batch fails with replace objects Christian Couder
2013-12-07 16:21 ` Christian Couder [this message]
2013-12-07 16:21 ` [PATCH v2 07/10] builtin/replace: teach listing using short, medium or full formats Christian Couder
2013-12-07 16:21 ` [PATCH v2 08/10] t6050: add tests for listing with --format Christian Couder
2013-12-09 3:19 ` Eric Sunshine
2013-12-09 5:58 ` Christian Couder
2013-12-07 16:21 ` [PATCH v2 09/10] builtin/replace: unset read_replace_refs Christian Couder
2013-12-07 19:02 ` Jakub Narebski
2013-12-07 19:37 ` Christian Couder
2013-12-07 16:21 ` [PATCH v2 10/10] Documentation/git-replace: describe --format option Christian Couder
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=20131207162106.21478.38769.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--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).