From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Document ls-files -t as obsolete.
Date: Wed, 14 Apr 2010 07:39:30 -0700 [thread overview]
Message-ID: <7vaat6qesd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1271252704-21739-1-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Wed\, 14 Apr 2010 15\:45\:04 +0200")
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> The behavior of "git ls-files -t" is very misleading (see
> http://thread.gmane.org/gmane.comp.version-control.git/126516 and
> http://thread.gmane.org/gmane.comp.version-control.git/144394/focus=144397
> for examples of mislead users) and badly documented, hence we point the
> users to superior alternatives.
I am no entirely happy with this patch.
If all your scripted Porcelain wants to see is "what are the paths I might
want to run 'git add' on?", you do not want to run diff twice (which is
what "status" does); you would say "ls-files -t -m -o --exclude-standard",
instead. The alternative is not even superiour in this case.
Having said that, I personally don't think of any other combination of
flags with which "ls-files -t" is useful.
If there are parts of the documentation that are misleading, perhaps that
is what your patch should be fixing instead, no?
next prev parent reply other threads:[~2010-04-14 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 13:45 [PATCH] Document ls-files -t as obsolete Matthieu Moy
2010-04-14 14:39 ` Junio C Hamano [this message]
2010-04-14 14:47 ` Daniel Grace
2010-04-14 14:55 ` Matthieu Moy
2010-04-14 14:47 ` Tor Arntsen
2010-04-14 14:58 ` Matthieu Moy
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=7vaat6qesd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.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