From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH v2] Document ls-files -t as semi-obsolete.
Date: Tue, 27 Jul 2010 17:06:38 -0400 [thread overview]
Message-ID: <20100727210638.GA12052@coredump.intra.peff.net> (raw)
In-Reply-To: <vpqeieoy9bb.fsf@bauges.imag.fr>
On Tue, Jul 27, 2010 at 10:11:04PM +0200, Matthieu Moy wrote:
> > Isn't "git diff-files --name-status" the closest plumbing analogue? Git
> > status actually does a lot of extra work.
>
> git diff-files --name-status won't show untracked files, while "git
> ls-files -t -o" will for example. I agree that "git status" does extra
> work, but that's what you usually want when you want to know the
> status of files. We already mention "git diff --name-status", so
> people looking for "git diff-tree --name-status" should be able to
> find it.
Good point. I was thinking of "ls-files -t" by itself, but you are
likely to ask for other things anyway.
> > Shouldn't one of them be marked "C"hanged (I think file2, but that was
> > what I was double-checking)?
>
> You should ask "git ls-files -t -m" if you want to see modified files.
OK, that makes sense, I guess.
> I'm afraid we have another proof that we should discourage the use of
> this feature ;-).
I think we all agree on that bit. :)
-Peff
prev parent reply other threads:[~2010-07-27 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 16:39 [PATCH v2] Document ls-files -t as semi-obsolete Matthieu Moy
2010-07-27 17:36 ` Junio C Hamano
2010-07-27 19:07 ` Michele Ballabio
2010-07-27 21:02 ` Matthieu Moy
2010-07-27 21:11 ` [PATCH v3] " Matthieu Moy
2010-07-28 4:00 ` Jeff King
2010-07-28 7:24 ` [PATCH v4] " Matthieu Moy
2010-07-27 19:58 ` [PATCH v2] " Jeff King
2010-07-27 20:11 ` Matthieu Moy
2010-07-27 21:06 ` Jeff King [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=20100727210638.GA12052@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.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).