git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teng Long <dyroneteng@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, avarab@gmail.com
Subject: Re: What's cooking in git.git (Mar 2022, #02; Mon, 7)
Date: Tue,  8 Mar 2022 16:05:51 +0800	[thread overview]
Message-ID: <20220308080551.18538-1-dyroneteng@gmail.com> (raw)
In-Reply-To: <xmqqilspp5yg.fsf@gitster.g>

Junio C Hamano wrote on Mon, 07 Mar 2022 17:51:19 -0800:

>[Stalled]
>
>* tl/ls-tree-oid-only (2022-03-04) 12 commits
> - ls-tree: support --object-only option for "git-ls-tree"
> - ls-tree: introduce "--format" option
> - cocci: allow padding with `strbuf_addf()`
> - ls-tree: introduce struct "show_tree_data"
> - ls-tree: slightly refactor `show_tree()`
> - ls-tree: fix "--name-only" and "--long" combined use bug
> - ls-tree: simplify nesting if/else logic in "show_tree()"
> - ls-tree: rename "retval" to "recurse" in "show_tree()"
> - ls-tree: use "size_t", not "int" for "struct strbuf"'s "len"
> - ls-tree: use "enum object_type", not {blob,tree,commit}_type
> - ls-tree: add missing braces to "else" arms
> - ls-tree: remove commented-out code
>
> "git ls-tree" learns "--oid-only" option, similar to "--name-only",
> and more generalized "--format" option.
> source: <cover.1646390152.git.dyroneteng@gmail.com>


Sorry for the late reply.

I posted a updated patchset last week, we already had a private review on that,
but maybe string need Ævar Arnfjörð Bjarmason for taking a look.

Thanks.

  reply	other threads:[~2022-03-08  8:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  1:51 What's cooking in git.git (Mar 2022, #02; Mon, 7) Junio C Hamano
2022-03-08  8:05 ` Teng Long [this message]
2022-03-09 19:14   ` Junio C Hamano
2022-03-08 16:08 ` ds/partial-bundles (was Re: What's cooking in git.git (Mar 2022, #02; Mon, 7)) Derrick Stolee
2022-03-09 16:12 ` jc/stash-drop " Phillip Wood
2022-03-09 17:10   ` Junio C Hamano
2022-03-09 18:03 ` ar/submodule-udpate " Glen Choo
2022-03-09 19:27   ` Junio C Hamano
2022-03-09 22:09     ` Glen Choo

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=20220308080551.18538-1-dyroneteng@gmail.com \
    --to=dyroneteng@gmail.com \
    --cc=avarab@gmail.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).