git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Teng Long <dyroneteng@gmail.com>
Cc: git@vger.kernel.org, tenglong.tl@alibaba-inc.com
Subject: Re: [PATCH 0/6] ls-tree.c: clean-up works
Date: Thu, 12 Jan 2023 16:02:13 +0100	[thread overview]
Message-ID: <230112.868ri723p0.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <20230112091135.20050-1-tenglong.tl@alibaba-inc.com>


On Thu, Jan 12 2023, Teng Long wrote:

> From: Teng Long <dyroneteng@gmail.com>
>
> This patchset aims to do works on refactoring and cleanup
> of ls-tree.c.
>
> The patches can be viewed as two parts:
>
>       * Part 1: from Ævar Arnfjörð Bjarmason which mentioned in
>       his RFC patchset[1] and Ævar suggests to submit a separate clean-up
>       series. After I read them, I accept them all.
>
>       * Part 2: fÆvarrom me which introduced in my RFC patchset[2] and after
>       I accepted Ævar's patches, I keep two patches from [2], the left
>       patches in [2] may no longer be needed.
>
> [1] https://public-inbox.org/git/RFC-cover-0.4-00000000000-20221117T134528Z-avarab@gmail.com/
> [2] https://public-inbox.org/git/20221117113023.65865-1-tenglong.tl@alibaba-inc.com/
>
> Thanks.

Thanks for picking this up. It would be great to have this queued up.

It looks good to me, although that's mostly self-approving, as the
range-diff between this and my [1] (and your description, but I wanted
to sanity check it) shows it's mostly the same changes:
	
p	1:  a7f86973d57 ! 1:  5004f03c4d2 ls-tree: don't use "show_tree_data" for "fast" callbacks
	    @@ Commit message
	     
	         1. https://lore.kernel.org/git/cover-0.7-00000000000-20220310T134811Z-avarab@gmail.com/
	     
	    +    Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
	    +    Signed-off-by: Teng Long <dyronteng@gmail.com>
	    +
	      ## builtin/ls-tree.c ##
	     @@ builtin/ls-tree.c: static int show_tree_fmt(const struct object_id *oid, struct strbuf *base,
	      	return recurse;
	2:  b046e6f5692 ! 2:  de5b4d0767a ls-tree: use a "struct options"
	    @@ Commit message
	         before, now it's just being brought to the surface.
	     
	         Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
	    +    Signed-off-by: Teng Long <dyroneteng@gmail.com>
	     
	      ## builtin/ls-tree.c ##
	     @@
	3:  329bc581b79 ! 3:  8f4b59183f6 ls-tree: fold "show_tree_data" into "cb" struct
	    @@ Commit message
	         we'll use only for that callback.
	     
	         Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
	    +    Signed-off-by: Teng Long <dyroneteng@gmail.com>
	     
	      ## builtin/ls-tree.c ##
	     @@ builtin/ls-tree.c: struct ls_tree_options {
	4:  de4f89645fa ! 4:  d701aceb101 ls-tree: make "line_termination" less generic
	    @@ Commit message
	         API itself does much the same thing.
	     
	         Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
	    +    Signed-off-by: Teng Long <dyroneteng@gmail.com>
	     
	      ## builtin/ls-tree.c ##
	     @@ builtin/ls-tree.c: static void expand_objectsize(struct strbuf *line, const struct object_id *oid,
	-:  ----------- > 5:  72bf99a1c74 ls-tree: cleanup the redundant SPACE
	-:  ----------- > 6:  978b89e5ea8 t3104: remove shift code in 'test_ls_tree_format'

I approve of that addition of the missing Signed-off-by (which I just
forgot about).

I left comments on the 2x new patches, but they were both nit-y
suggestions for maybe rephrasing the commit messages a bit, but as noted
I don't think it's worth another re-roll (just maybe if others comment
on the other patches and/or find other issues worth re-rolling).

      parent reply	other threads:[~2023-01-12 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  9:11 [PATCH 0/6] ls-tree.c: clean-up works Teng Long
2023-01-12  9:11 ` [PATCH 1/6] ls-tree: don't use "show_tree_data" for "fast" callbacks Teng Long
2023-01-12  9:11 ` [PATCH 2/6] ls-tree: use a "struct options" Teng Long
2023-01-12  9:11 ` [PATCH 3/6] ls-tree: fold "show_tree_data" into "cb" struct Teng Long
2023-01-12  9:11 ` [PATCH 4/6] ls-tree: make "line_termination" less generic Teng Long
2023-01-12  9:11 ` [PATCH 5/6] ls-tree: cleanup the redundant SPACE Teng Long
2023-01-12 14:53   ` Ævar Arnfjörð Bjarmason
2023-01-12  9:11 ` [PATCH 6/6] t3104: remove shift code in 'test_ls_tree_format' Teng Long
2023-01-12 14:56   ` Ævar Arnfjörð Bjarmason
2023-01-12 15:02 ` Ævar Arnfjörð Bjarmason [this message]

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=230112.868ri723p0.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=dyroneteng@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tenglong.tl@alibaba-inc.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).