From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: [PATCH] ls-tree: --name-only
Date: Thu, 01 Dec 2005 14:56:41 -0800 [thread overview]
Message-ID: <7v8xv4ctp2.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512011354500.3099@g5.osdl.org> (Linus Torvalds's message of "Thu, 1 Dec 2005 13:57:29 -0800 (PST)")
Fingers of some "git diff" users are trained to do --name-only
which git-ls-tree unfortunately does not take. With this,
cd sub/directory && git-ls-tree -r --name-only HEAD -- ..
would show only the paths but not object names nor modes. I
threw in another synonym --name-status only for usability, but
obviously ls-tree does not do any comparison so what it does is
the same as --name-only.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
Linus Torvalds <torvalds@osdl.org> writes:
> That brings up another issue. I typed
>
> git-ls-tree -r --name-only ..
>
> and it obviously didn't work. That's kind of sad. I use that quite a lot
> for "git diff", for example, because quite often I want to see the files,
> but I don't care about anything else.
ls-tree.c | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
c639a5548a5d8414b55202592885449f66ee2f33
diff --git a/ls-tree.c b/ls-tree.c
index 07db863..dae377d 100644
--- a/ls-tree.c
+++ b/ls-tree.c
@@ -12,11 +12,12 @@ static int line_termination = '\n';
#define LS_RECURSIVE 1
#define LS_TREE_ONLY 2
#define LS_SHOW_TREES 4
+#define LS_NAME_ONLY 8
static int ls_options = 0;
const char **pathspec;
static const char ls_tree_usage[] =
- "git-ls-tree [-d] [-r] [-t] [-z] <tree-ish> [path...]";
+ "git-ls-tree [-d] [-r] [-t] [-z] [--name-only] [--name-status] <tree-ish> [path...]";
static int show_recursive(const char *base, int baselen, const char *pathname)
{
@@ -64,7 +65,8 @@ static int show_tree(unsigned char *sha1
else if (ls_options & LS_TREE_ONLY)
return 0;
- printf("%06o %s %s\t", mode, type, sha1_to_hex(sha1));
+ if (!(ls_options & LS_NAME_ONLY))
+ printf("%06o %s %s\t", mode, type, sha1_to_hex(sha1));
write_name_quoted(base, baselen, pathname, line_termination, stdout);
putchar(line_termination);
return retval;
@@ -92,6 +94,13 @@ int main(int argc, const char **argv)
case 't':
ls_options |= LS_SHOW_TREES;
break;
+ case '-':
+ if (!strcmp(argv[1]+2, "name-only") ||
+ !strcmp(argv[1]+2, "name-status")) {
+ ls_options |= LS_NAME_ONLY;
+ break;
+ }
+ /* otherwise fallthru */
default:
usage(ls_tree_usage);
}
--
0.99.9.GIT
next prev parent reply other threads:[~2005-12-01 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 22:57 What's new in git.git master branch Junio C Hamano
2005-12-01 8:54 ` Fredrik Kuivinen
2005-12-01 9:38 ` Junio C Hamano
2005-12-02 5:45 ` Junio C Hamano
2005-12-02 5:46 ` Junio C Hamano
2005-12-02 8:46 ` Fredrik Kuivinen
2005-12-02 8:36 ` Fredrik Kuivinen
2005-12-07 10:01 ` [PATCH 3/3] update-index: allow --index-info to add higher stages Junio C Hamano
2005-12-01 18:35 ` git-ls-tree: add "-t" option to always show the tree entries Linus Torvalds
2005-12-01 21:15 ` Junio C Hamano
2005-12-01 21:57 ` Linus Torvalds
2005-12-01 22:04 ` Junio C Hamano
2005-12-01 22:56 ` Junio C Hamano [this message]
2005-12-02 22:12 ` Junio C Hamano
2005-12-02 23:11 ` Linus Torvalds
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=7v8xv4ctp2.fsf_-_@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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