From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 0/6] Hash Abstraction
Date: Sun, 20 Aug 2017 17:18:14 -0700 [thread overview]
Message-ID: <xmqqefs57ozd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170821000022.26729-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Mon, 21 Aug 2017 00:00:16 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> brian m. carlson (6):
> vcs-svn: remove unused prototypes
> vcs-svn: rename repo functions to "svn_repo"
> setup: expose enumerated repo info
> Add structure representing hash algorithm
> Integrate hash algorithm support with repo setup
> Switch empty tree and blob lookups to use hash abstraction
The first two are about very quiescent code that can go in and sail
thru 'next' very quickly without problems, I would think.
After the third one alone, the discovered format information may not
be fully plumbed through (i.e. after setup finishes there is no way
for outside callers to peek at the repo_fmt instance that was on
stack), but it seems that this is sufficient for the purpose of this
step and it looks a very sensible first step.,
As to patch 4, I tend to agree with the analysis you had in this
cover letter--it did make me wonder if we want to have union of hash
contenxt structures, for example. But the enumeration of virtual
functions looks about right.
I wondered if we wanted "binery size" and "hex size" separately,
because the latter will always be twice as big as the former as long
as the latter's definition is "hex", but that is a minor point.
Thanks for starting this.
> builtin/am.c | 2 +-
> builtin/checkout.c | 2 +-
> builtin/diff.c | 2 +-
> builtin/pull.c | 2 +-
> cache.h | 48 ++++++++++++++++++++++++++++++++++++++++++++----
> diff-lib.c | 2 +-
> merge-recursive.c | 2 +-
> notes-merge.c | 2 +-
> repository.c | 7 +++++++
> repository.h | 5 +++++
> sequencer.c | 6 +++---
> setup.c | 48 +++++++++++++++++++++++++++---------------------
> sha1_file.c | 29 +++++++++++++++++++++++++++++
> submodule.c | 2 +-
> vcs-svn/repo_tree.c | 6 +++---
> vcs-svn/repo_tree.h | 13 +++----------
> vcs-svn/svndump.c | 8 ++++----
> 17 files changed, 133 insertions(+), 53 deletions(-)
next prev parent reply other threads:[~2017-08-21 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 0:00 [RFC PATCH 0/6] Hash Abstraction brian m. carlson
2017-08-21 0:00 ` [RFC PATCH 1/6] vcs-svn: remove unused prototypes brian m. carlson
2017-08-21 0:00 ` [RFC PATCH 2/6] vcs-svn: rename repo functions to "svn_repo" brian m. carlson
2017-08-21 0:00 ` [RFC PATCH 3/6] setup: expose enumerated repo info brian m. carlson
2017-08-21 0:00 ` [RFC PATCH 4/6] Add structure representing hash algorithm brian m. carlson
2017-08-21 21:08 ` Stefan Beller
2017-08-21 0:00 ` [RFC PATCH 5/6] Integrate hash algorithm support with repo setup brian m. carlson
2017-08-21 21:16 ` Stefan Beller
2017-08-21 0:00 ` [RFC PATCH 6/6] Switch empty tree and blob lookups to use hash abstraction brian m. carlson
2017-08-21 0:18 ` Junio C Hamano [this message]
2017-08-21 20:48 ` [RFC PATCH 0/6] Hash Abstraction Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqefs57ozd.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).