From: Jason McMullan <jason.mcmullan@timesys.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH-RFC] Rewrite ls-tree to behave more like "/bin/ls -a"
Date: Sat, 28 May 2005 18:02:08 -0400 [thread overview]
Message-ID: <1117317729.11542.32.camel@jmcmullan.timesys> (raw)
In-Reply-To: <7vll5zygn1.fsf_-_@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Sat, 2005-05-28 at 00:05 -0700, Junio C Hamano wrote:
> - Unlike the old ls-tree behaviour that used paths arguments to
> restrict output (not that it worked as intended---as pointed
> out in the mailing list discussion, it was quite incoherent),
> this rewrite uses paths arguments to specify what to show.
>
> - Without arguments, it implicitly uses the root level as its
> sole argument ("/bin/ls -a" behaves as if "." is given
> without argument).
>
> - Without -r (recursive) flag, it shows the named blob (either
> file or symlink), or the named tree and its immediate
> children.
>
> - With -r flag, it shows the named path, and recursively
> descends into it if it is a tree.
>
> - With -d flag, it shows the named path and does not show its
> children even if the path is a tree, nor descends into it
> recursively.
This behavior pattern is very agreeable. I'll take it!
Consider your patch:
Signed-Off-By: Jason McMullan <jason.mcmullan@timesys.com>
--
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-28 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 12:08 [PATCH] ls-tree path restriction semantics fixes Jason McMullan
2005-05-27 18:16 ` Junio C Hamano
2005-05-27 19:26 ` Jason McMullan
2005-05-28 3:31 ` Junio C Hamano
2005-05-28 7:05 ` [PATCH-RFC] Rewrite ls-tree to behave more like "/bin/ls -a" Junio C Hamano
2005-05-28 22:02 ` Jason McMullan [this message]
2005-05-29 18:44 ` Junio C Hamano
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=1117317729.11542.32.camel@jmcmullan.timesys \
--to=jason.mcmullan@timesys.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).