git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Teng Long <dyroneteng@gmail.com>
To: git@vger.kernel.org
Cc: avarab@gmail.com, dyroneteng@gmail.com, tenglong.tl@alibaba-inc.com
Subject: [PATCH 0/6] ls-tree.c: clean-up works
Date: Thu, 12 Jan 2023 17:11:29 +0800	[thread overview]
Message-ID: <20230112091135.20050-1-tenglong.tl@alibaba-inc.com> (raw)

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.

Teng Long (2):
  ls-tree: cleanup the redundant SPACE
  t3104: remove shift code in 'test_ls_tree_format'

Ævar Arnfjörð Bjarmason (4):
  ls-tree: don't use "show_tree_data" for "fast" callbacks
  ls-tree: use a "struct options"
  ls-tree: fold "show_tree_data" into "cb" struct
  ls-tree: make "line_termination" less generic

 builtin/ls-tree.c         | 257 ++++++++++++++++++++++----------------
 t/t3104-ls-tree-format.sh |   1 -
 2 files changed, 150 insertions(+), 108 deletions(-)

-- 
2.39.0.98.g174eaa53973.dirty


             reply	other threads:[~2023-01-12  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  9:11 Teng Long [this message]
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 ` [PATCH 0/6] ls-tree.c: clean-up works Ævar Arnfjörð Bjarmason

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=20230112091135.20050-1-tenglong.tl@alibaba-inc.com \
    --to=dyroneteng@gmail.com \
    --cc=avarab@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.
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).