From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH 2/2] Convert read_tree{,_recursive} to support struct pathspec
Date: Thu, 24 Mar 2011 21:49:52 +0700 [thread overview]
Message-ID: <20110324144952.GA24388@do> (raw)
In-Reply-To: <1300977675-6243-2-git-send-email-pclouds@gmail.com>
On Thu, Mar 24, 2011 at 09:41:15PM +0700, Nguyễn Thái Ngọc Duy wrote:
> All callers are updated.
Jeez.. I made last minute changes and it broke something. This should
be squashed in, because tree_entry_interesting() does not like struct
pathspec* == NULL.
--8<--
diff --git a/builtin/log.c b/builtin/log.c
index 796e9e5..cff39cf 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -396,6 +396,7 @@ int cmd_show(int argc, const char **argv, const char *prefix)
struct rev_info rev;
struct object_array_entry *objects;
struct setup_revision_opt opt;
+ struct pathspec match_all;
int i, count, ret = 0;
git_config(git_log_config, NULL);
@@ -403,6 +404,7 @@ int cmd_show(int argc, const char **argv, const char *prefix)
if (diff_use_color_default == -1)
diff_use_color_default = git_use_color_default;
+ init_pathspec(&match_all, NULL);
init_revisions(&rev, prefix);
rev.diff = 1;
rev.always_show_header = 1;
@@ -449,7 +451,7 @@ int cmd_show(int argc, const char **argv, const char *prefix)
diff_get_color_opt(&rev.diffopt, DIFF_COMMIT),
name,
diff_get_color_opt(&rev.diffopt, DIFF_RESET));
- read_tree_recursive((struct tree *)o, "", 0, 0, NULL,
+ read_tree_recursive((struct tree *)o, "", 0, 0, &match_all,
show_tree_object, NULL);
rev.shown_one = 1;
break;
--8<--
--
Duy
next prev parent reply other threads:[~2011-03-24 14:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 10:33 Relative ls-files John Tapsell
2011-03-23 10:49 ` Michael J Gruber
2011-03-23 11:27 ` John Tapsell
2011-03-23 11:28 ` demerphq
2011-03-23 11:42 ` Michael J Gruber
2011-03-23 13:54 ` Martin Langhoff
2011-03-23 14:09 ` Junio C Hamano
2011-03-23 14:14 ` Nguyen Thai Ngoc Duy
2011-03-23 15:20 ` Junio C Hamano
2011-03-23 15:41 ` Nguyen Thai Ngoc Duy
2011-03-23 22:44 ` Junio C Hamano
2011-03-24 13:26 ` Nguyen Thai Ngoc Duy
2011-03-24 14:41 ` [PATCH 1/2] Reimplement read_tree_recursive() using tree_entry_interesting() Nguyễn Thái Ngọc Duy
2011-03-24 14:41 ` [PATCH 2/2] Convert read_tree{,_recursive} to support struct pathspec Nguyễn Thái Ngọc Duy
2011-03-24 14:49 ` Nguyen Thai Ngoc Duy [this message]
2011-03-24 19:58 ` Junio C Hamano
2011-03-24 19:07 ` [PATCH 1/2] Reimplement read_tree_recursive() using tree_entry_interesting() Junio C Hamano
2011-03-24 19:55 ` Junio C Hamano
2011-03-25 9:34 ` [PATCH 1/3] " Nguyễn Thái Ngọc Duy
2011-03-25 9:34 ` [PATCH 2/3] Convert read_tree{,_recursive} to support struct pathspec Nguyễn Thái Ngọc Duy
2011-03-25 9:34 ` [PATCH 3/3] Improve tree_entry_interesting() handling code Nguyễn Thái Ngọc Duy
2011-03-24 14:47 ` Relative ls-files Junio C Hamano
2011-03-23 14:46 ` Martin Langhoff
2011-03-23 15:24 ` Junio C Hamano
2011-03-23 17:35 ` Junio C Hamano
2011-03-23 15:42 ` Junio C Hamano
2011-03-23 15:57 ` Michael J Gruber
2011-03-23 16:10 ` Nguyen Thai Ngoc Duy
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=20110324144952.GA24388@do \
--to=pclouds@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).