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>,
Eric Sunshine <sunshine@sunshineco.com>,
Karsten Blees <karsten.blees@gmail.com>
Subject: [PATCH v4 03/10] Introduce lookup_replace_object_extended() to pass flags
Date: Sat, 28 Dec 2013 12:00:08 +0100 [thread overview]
Message-ID: <20131228110016.2272.47632.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20131228105505.2272.58873.chriscool@tuxfamily.org>
Currently, there is only one caller to lookup_replace_object()
that can benefit from passing it some flags, but we expect
that there could be more.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
cache.h | 6 ++++++
sha1_file.c | 3 +--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/cache.h b/cache.h
index 873a6b5..563f85f 100644
--- a/cache.h
+++ b/cache.h
@@ -773,6 +773,12 @@ static inline const unsigned char *lookup_replace_object(const unsigned char *sh
return sha1;
return do_lookup_replace_object(sha1);
}
+static inline const unsigned char *lookup_replace_object_extended(const unsigned char *sha1, unsigned flag)
+{
+ if (! (flag & LOOKUP_REPLACE_OBJECT))
+ return sha1;
+ return lookup_replace_object(sha1);
+}
/* Read and unpack a sha1 file into memory, write memory to a sha1 file */
extern int sha1_object_info(const unsigned char *, unsigned long *);
diff --git a/sha1_file.c b/sha1_file.c
index 76e9f32..4fb2f17 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -2591,8 +2591,7 @@ void *read_sha1_file_extended(const unsigned char *sha1,
void *data;
char *path;
const struct packed_git *p;
- const unsigned char *repl = (flag & LOOKUP_REPLACE_OBJECT)
- ? lookup_replace_object(sha1) : sha1;
+ const unsigned char *repl = lookup_replace_object_extended(sha1, flag);
errno = 0;
data = read_object(repl, type, size);
--
1.8.4.1.616.g07f5c81
next prev parent reply other threads:[~2013-12-28 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 11:00 [PATCH v4 00/10] teach replace objects to sha1_object_info_extended() Christian Couder
2013-12-28 11:00 ` [PATCH v4 01/10] Rename READ_SHA1_FILE_REPLACE flag to LOOKUP_REPLACE_OBJECT Christian Couder
2013-12-28 11:00 ` [PATCH v4 02/10] replace_object: don't check read_replace_refs twice Christian Couder
2013-12-28 11:00 ` Christian Couder [this message]
2013-12-28 11:00 ` [PATCH v4 04/10] Add an "unsigned flags" parameter to sha1_object_info_extended() Christian Couder
2013-12-28 11:00 ` [PATCH v4 05/10] t6050: show that git cat-file --batch fails with replace objects Christian Couder
2013-12-28 11:00 ` [PATCH v4 06/10] sha1_file: perform object replacement in sha1_object_info_extended() Christian Couder
2013-12-28 11:00 ` [PATCH v4 07/10] builtin/replace: teach listing using short, medium or long formats Christian Couder
2013-12-28 11:00 ` [PATCH v4 08/10] t6050: add tests for listing with --format Christian Couder
2013-12-28 11:00 ` [PATCH v4 09/10] builtin/replace: unset read_replace_refs Christian Couder
2013-12-28 11:00 ` [PATCH v4 10/10] Documentation/git-replace: describe --format option Christian Couder
2013-12-30 20:32 ` [PATCH v4 00/10] teach replace objects to sha1_object_info_extended() Junio C Hamano
2013-12-31 6:23 ` 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=20131228110016.2272.47632.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--cc=karsten.blees@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).