From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2024, #04; Fri, 12)
Date: Tue, 16 Jul 2024 08:16:09 -0700 [thread overview]
Message-ID: <047b889e-fa6d-4c4a-b486-0bc80922c4ca@github.com> (raw)
In-Reply-To: <xmqqbk31b6le.fsf@gitster.g>
Junio C Hamano wrote:
> * vd/mktree (2024-06-20) 17 commits
> - mktree: remove entries when mode is 0
> - mktree: allow deeper paths in input
> - mktree: optionally add to an existing tree
> - mktree: add directory-file conflict hashmap
> - mktree: use iterator struct to add tree entries to index
> - mktree: create tree using an in-core index
> - mktree: overwrite duplicate entries
> - mktree: validate paths more carefully
> - mktree: add a --literally option
> - mktree.c: do not fail on mismatched submodule type
> - mktree: use read_index_info to read stdin lines
> - index-info.c: parse object type in provided in read_index_info
> - index-info.c: return unrecognized lines to caller
> - update-index: generalize 'read_index_info'
> - mktree: use non-static tree_entry array
> - mktree: rename treeent to tree_entry
> - mktree: use OPT_BOOL
>
> "git mktree" has been rewritten, taking advantage of the cache-tree
> API.
>
> Will merge to 'next'?
> source: <pull.1746.v2.git.1718834285.gitgitgadget@gmail.com>
Please drop this series; I haven't had any time to work on it since your
latest comments, and likely won't for the foreseeable future. If I do find
some time to address those comments, I'll resubmit the series.
Thanks!
next prev parent reply other threads:[~2024-07-16 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 16:27 What's cooking in git.git (Jul 2024, #04; Fri, 12) Junio C Hamano
2024-07-16 13:26 ` Ghanshyam Thakkar
2024-07-16 15:18 ` Junio C Hamano
2024-07-16 15:16 ` Victoria Dye [this message]
2024-07-16 15:18 ` 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=047b889e-fa6d-4c4a-b486-0bc80922c4ca@github.com \
--to=vdye@github.com \
--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).