git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Darrin Thompson <darrint@progeny.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-ls-files -o no recurse?
Date: Sat, 7 Jan 2006 11:34:24 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601071131570.3169@g5.osdl.org> (raw)
In-Reply-To: <7vace7khbi.fsf@assigned-by-dhcp.cox.net>



On Sat, 7 Jan 2006, Junio C Hamano wrote:
> 
> I have been unsure about the name "--directory", like you said.

Well, I didn't like "--directory" either, but couldn't come up with 
anything better. How about just "--no-recurse", which is not technically 
accurate (we always recurse into directories we know about), but might be 
more understandable.

The reason I called it "--directory" was that it would talk about 
directories that it doesn't know about (as opposed to individual files it 
doesn't know about). So "--other --directory" kind of makes sense if you 
read it that way ("show files and directories we don't know about").

But yeah, it's not a great name.

		Linus

      reply	other threads:[~2006-01-07 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 18:51 git-ls-files -o no recurse? Darrin Thompson
2006-01-04 21:31 ` Linus Torvalds
2006-01-05 17:15   ` Darrin Thompson
2006-01-05 17:31     ` Linus Torvalds
2006-01-06 22:38   ` Junio C Hamano
2006-01-07 18:20     ` Darrin Thompson
2006-01-07 18:23     ` Darrin Thompson
2006-01-07 18:45       ` Junio C Hamano
2006-01-07 19:34         ` Linus Torvalds [this message]

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=Pine.LNX.4.64.0601071131570.3169@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=darrint@progeny.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).