From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-ls-files.txt: clarify what "other files" mean for --other
Date: Fri, 07 Aug 2009 10:15:01 +0200 [thread overview]
Message-ID: <vpqprb8xcoq.fsf@bauges.imag.fr> (raw)
In-Reply-To: <7vmy6cfz9j.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu\, 06 Aug 2009 13\:44\:40 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>
>> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
>> ---
>> Actually, if it was not about backward compatibility, I'd just replace
>> -o, --other with -u, --untracked and talk about "untracked" everywhere,
>> but compatibility matters more than consistancy for plumbing.
>
> "ls-files -u" talks about (u)nmerged files.
(forgot this, so -u is even less an option)
> What consistency did you have in mind?
I found no place outside git ls-files where Git talks about "other"
files. Everywhere else, it talks about Untracked files.
As for the -u option, git status/commit -u[mode] is for Untracked
files, not unmerged ones.
--
Matthieu
prev parent reply other threads:[~2009-08-07 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 15:11 [PATCH] git-ls-files.txt: clarify what "other files" mean for --other Matthieu Moy
2009-08-06 20:44 ` Junio C Hamano
2009-08-07 8:15 ` Matthieu Moy [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=vpqprb8xcoq.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--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).