git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 (Mar 2017, #03; Wed, 8)
Date: Thu, 9 Mar 2017 01:01:52 +0000	[thread overview]
Message-ID: <20170309010152.klyhhth3ekm2iia2@genre.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqvarjz5yv.fsf@gitster.mtv.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Wed, Mar 08, 2017 at 03:47:20PM -0800, Junio C Hamano wrote:
> * bc/object-id (2017-02-22) 19 commits
>  - wt-status: convert to struct object_id
>  - builtin/merge-base: convert to struct object_id
>  - Convert object iteration callbacks to struct object_id
>  - sha1_file: introduce an nth_packed_object_oid function
>  - refs: simplify parsing of reflog entries
>  - refs: convert each_reflog_ent_fn to struct object_id
>  - reflog-walk: convert struct reflog_info to struct object_id
>  - builtin/replace: convert to struct object_id
>  - Convert remaining callers of resolve_refdup to object_id
>  - builtin/merge: convert to struct object_id
>  - builtin/clone: convert to struct object_id
>  - builtin/branch: convert to struct object_id
>  - builtin/grep: convert to struct object_id
>  - builtin/fmt-merge-message: convert to struct object_id
>  - builtin/fast-export: convert to struct object_id
>  - builtin/describe: convert to struct object_id
>  - builtin/diff-tree: convert to struct object_id
>  - builtin/commit: convert to struct object_id
>  - hex: introduce parse_oid_hex
> 
>  "uchar [40]" to "struct object_id" conversion continues.
> 
>  Now at v5.
>  cf. <20170221234737.894681-1-sandals@crustytoothpaste.net>

Were you expecting more work on this series?  I believe I've addressed
all the review comments that were outstanding, but if I've missed
something, please let me know.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

  parent reply	other threads:[~2017-03-09  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 23:47 What's cooking in git.git (Mar 2017, #03; Wed, 8) Junio C Hamano
2017-03-09  0:46 ` Jonathan Tan
2017-03-09  1:01 ` brian m. carlson [this message]
2017-03-10 19:53   ` Junio C Hamano
2017-03-09 22:00 ` Johannes Schindelin

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=20170309010152.klyhhth3ekm2iia2@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.
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).