From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/5] Updates to replace-object API
Date: Sun, 15 May 2011 12:54:49 -0700 [thread overview]
Message-ID: <1305489294-14341-1-git-send-email-gitster@pobox.com> (raw)
While I was looking at gaining a low-level access to read from the object
store, I found a handful poorly-designed part in the internal API to deal
with object replacement.
Junio C Hamano (5):
Declare lookup_replace_object() in cache.h, not in commit.h
t6050: make sure we test not just commit replacement
read_sha1_file(): get rid of read_sha1_file_repl() madness
inline lookup_replace_object() calls
read_sha1_file(): allow selective bypassing of replacement mechanism
builtin/mktag.c | 4 ++--
cache.h | 18 ++++++++++++++----
commit.h | 2 --
environment.c | 2 +-
object.c | 4 ++--
replace_object.c | 4 +++-
sha1_file.c | 16 +++++++---------
t/t6050-replace.sh | 18 ++++++++++++++++--
8 files changed, 45 insertions(+), 23 deletions(-)
--
1.7.5.1.334.gdfd07
next reply other threads:[~2011-05-15 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 19:54 Junio C Hamano [this message]
2011-05-15 19:54 ` [PATCH 1/5] Declare lookup_replace_object() in cache.h, not in commit.h Junio C Hamano
2011-05-15 19:54 ` [PATCH 2/5] t6050: make sure we test not just commit replacement Junio C Hamano
2011-05-15 19:54 ` [PATCH 3/5] read_sha1_file(): get rid of read_sha1_file_repl() madness Junio C Hamano
2011-05-15 19:54 ` [PATCH 4/5] inline lookup_replace_object() calls Junio C Hamano
2011-05-15 19:54 ` [PATCH 5/5] read_sha1_file(): allow selective bypassing of replacement mechanism 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=1305489294-14341-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--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).