From: Teng Long <dyroneteng@gmail.com>
To: dyroneteng@gmail.com
Cc: git@vger.kernel.org, peff@peff.net
Subject: [PATCH v3 0/1] list-objects.c: rename "traverse_trees_and_blobs" to "traverse_non_commits"
Date: Thu, 12 Aug 2021 16:59:30 +0800 [thread overview]
Message-ID: <cover.1628758416.git.dyroneteng@gmail.com> (raw)
In-Reply-To: <cover.1628757762.git.dyroneteng@gmail.com>
Patch-v3 fix the indent problem in v2.
Teng Long (1):
list-objects.c: rename "traverse_trees_and_blobs" to
"traverse_non_commits"
list-objects.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Range-diff against v2:
1: 2d19f0901c ! 1: 8548aa8bb1 list-objects.c: rename "traverse_trees_and_blobs" to "traverse_non_commits"
@@ list-objects.c: static void add_pending_tree(struct rev_info *revs, struct tree
}
-static void traverse_trees_and_blobs(struct traversal_context *ctx,
+- struct strbuf *base)
+static void traverse_non_commits(struct traversal_context *ctx,
- struct strbuf *base)
++ struct strbuf *base)
{
int i;
+
@@ list-objects.c: static void do_traverse(struct traversal_context *ctx)
* needs a reallocation for each commit. Can we pass the
* tree directory without allocation churn?
--
2.32.0.1.g4c9ac18d93.dirty
next prev parent reply other threads:[~2021-08-12 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 9:07 [PATCH v1 0/1] traverse_trees_and_blobs: rename and tree-wide Teng Long
2021-08-11 9:07 ` [PATCH v1 1/1] list-objects.c: " Teng Long
2021-08-11 18:00 ` Junio C Hamano
2021-08-11 19:11 ` Jeff King
2021-08-12 8:05 ` Teng Long
2021-08-12 7:54 ` Teng Long
2021-08-12 8:47 ` [PATCH v2 0/1] list-objects.c: rename "traverse_trees_and_blobs" to "traverse_non_commits" Teng Long
2021-08-12 8:47 ` [PATCH v2 1/1] " Teng Long
2021-08-12 8:59 ` Teng Long [this message]
2021-08-12 8:59 ` [PATCH v3 " Teng Long
2021-08-12 19:24 ` Jeff King
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=cover.1628758416.git.dyroneteng@gmail.com \
--to=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).