Re: [RFC PATCH 2/3] sha1-array: support appending unsigned char hash
- From
Stefan Beller <sbeller@google.com>
- Date
- Jul 11, 2017, 22:06 UTC
- Message-ID
- <CAGZ79kZ9Ewxv=8fnRZZaQjpyAdv8df81a9aLRkJzEt5ZU0VcTA@mail.gmail.com>
- In-Reply-To
- <523f64e1395124a02316071329bedf9884757479.1499800530.git.jonathantanmy@google.com>
On Tue, Jul 11, 2017 at 12:48 PM, Jonathan Tan <jonathantanmy@google.com> wrote:
Show 5 quoted lines
> In a subsequent patch, sha1_file will need to append object names in the > form of "unsigned char *" to oid arrays. Teach sha1-array support for > that. > > Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
This breaks the oid/sha1 barrier?
I would have expected the caller to do a
oid_array_append_oid(&array, sha1_to_oid(sha1));
with sha1_to_oid working off some static memory, such that the call to oid_array_append_oid (which we have as oid_array_append) is just as cheap?
Could you say more in the commit message on why we collude sha1 and oids here?
Thanks, Stefan