From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2018, #03; Wed, 25)
Date: Thu, 26 Apr 2018 01:13:37 +0000 [thread overview]
Message-ID: <20180426011337.GA722934@genre.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqmuxr4r6n.fsf@gitster-ct.c.googlers.com>
[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]
On Wed, Apr 25, 2018 at 05:37:52PM +0900, Junio C Hamano wrote:
> * bc/object-id (2018-04-24) 41 commits
> - merge-one-file: compute empty blob object ID
> - add--interactive: compute the empty tree value
> - Update shell scripts to compute empty tree object ID
> - sha1_file: only expose empty object constants through git_hash_algo
> - dir: use the_hash_algo for empty blob object ID
> - sequencer: use the_hash_algo for empty tree object ID
> - cache-tree: use is_empty_tree_oid
> - sha1_file: convert cached object code to struct object_id
> - builtin/reset: convert use of EMPTY_TREE_SHA1_BIN
> - builtin/receive-pack: convert one use of EMPTY_TREE_SHA1_HEX
> - wt-status: convert two uses of EMPTY_TREE_SHA1_HEX
> - submodule: convert several uses of EMPTY_TREE_SHA1_HEX
> - sequencer: convert one use of EMPTY_TREE_SHA1_HEX
> - merge: convert empty tree constant to the_hash_algo
> - builtin/merge: switch tree functions to use object_id
> - builtin/am: convert uses of EMPTY_TREE_SHA1_BIN to the_hash_algo
> - builtin/receive-pack: avoid hard-coded constants for push certs
> - diff: specify abbreviation size in terms of the_hash_algo
> - upload-pack: replace use of several hard-coded constants
> - revision: replace use of hard-coded constants
> - http: eliminate hard-coded constants
> - dir: convert struct untracked_cache_dir to object_id
> - commit: convert uses of get_sha1_hex to get_oid_hex
> - index-pack: abstract away hash function constant
> - pack-redundant: convert linked lists to use struct object_id
> - Update struct index_state to use struct object_id
> - split-index: convert struct split_index to object_id
> - submodule-config: convert structures to object_id
> - fsck: convert static functions to struct object_id
> - tree-walk: convert get_tree_entry_follow_symlinks to object_id
> - tree-walk: avoid hard-coded 20 constant
> - pack-redundant: abstract away hash algorithm
> - pack-objects: abstract away hash algorithm
> - packfile: abstract away hash constant values
> - packfile: convert find_pack_entry to object_id
> - sha1_file: convert freshen functions to object_id
> - packfile: convert has_sha1_pack to object_id
> - packfile: remove unused member from struct pack_entry
> - Remove unused member in struct object_context
> - server-info: remove unused members from struct pack_info
> - cache: add a function to read an object ID from a buffer
>
> Conversion from uchar[20] to struct object_id continues.
I do plan to reroll this, and if you want to forge my sign-off on the
patch I missed in the mean time, please do.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-04-26 1:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 8:37 What's cooking in git.git (Apr 2018, #03; Wed, 25) Junio C Hamano
2018-04-25 10:35 ` Ævar Arnfjörð Bjarmason
2018-04-25 17:43 ` Brandon Williams
2018-04-26 12:44 ` Derrick Stolee
2018-04-27 7:02 ` Johannes Schindelin
2018-04-25 12:37 ` js/rebase-recreate-merge, was " Johannes Schindelin
2018-04-25 16:21 ` Elijah Newren
2018-04-26 4:39 ` Junio C Hamano
2018-04-26 1:13 ` brian m. carlson [this message]
2018-04-26 15:26 ` Duy Nguyen
2018-04-27 7:39 ` Eric Sunshine
2018-04-30 0:03 ` 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=20180426011337.GA722934@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).