From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2015, #06; Sun, 22)
Date: Mon, 23 Feb 2015 11:00:21 -0800 [thread overview]
Message-ID: <xmqqk2z8tpve.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54EB30F0.4010404@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 23 Feb 2015 14:53:52 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> status, status -s and the like are in an ordinary user's tool box.
> ls-files isn't, at least not with "-t", which we even mark as deprecated.
>
> That makes me wonder, though, how difficult it would be to
> wt_status_collect_unchanged() and to leverage the status machinery
> rather than ls-files.
Good point. wt-status feels like a much better infrastructure to
build on than "ls-files -t", which should die ;-). Especially if
the command is interested in showing the state of the working tree
files relative to the tree of HEAD, as "ls-files" is purely between
the index and the working tree.
next prev parent reply other threads:[~2015-02-23 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 21:41 What's cooking in git.git (Feb 2015, #06; Sun, 22) Junio C Hamano
2015-02-23 13:53 ` Michael J Gruber
2015-02-23 19:00 ` Junio C Hamano [this message]
2015-02-23 20:27 ` Jeff King
2015-02-25 10:20 ` Duy Nguyen
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=xmqqk2z8tpve.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.