From: Constantine Plotnikov <constantine.plotnikov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jon Seymour <jon.seymour@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git-ls-files --added?
Date: Mon, 25 May 2009 11:31:42 +0400 [thread overview]
Message-ID: <85647ef50905250031m375a14d9y252444a8bdc250b5@mail.gmail.com> (raw)
In-Reply-To: <7vws85y9n7.fsf@alter.siamese.dyndns.org>
On Mon, May 25, 2009 at 10:33 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Jon Seymour <jon.seymour@gmail.com> writes:
>> ...
>>> I am still interested in the rationale for git-ls-files not supporting
>>> such an option directly, since git-diff still seems a little indirect.
>>
>> Partly historical, but more fundamental reason is because ls-files
>> plumbing is about the index.
>> ...
>> Added is _not_ about comparision between the index and the work tree. It
>> is between the HEAD commit and the index, and it does not belong to
>> ls-files plumbing.
>
> Having said all that, I think you might be interested in pursuing
>
> http://thread.gmane.org/gmane.comp.version-control.git/97830/focus=99134
>
> Also, the following thread may serve as a food for thought; it shows that
> there is real need for some concise, easy to parse output for people who
> want their own Porcelain.
>
> http://thread.gmane.org/gmane.comp.version-control.git/106122/focus=108110
>
> In short, ls-files and diff-index _can_ give you what you want, but often
> people would want information from both, consolidated.
I'm one of those people :) Writing git support for IDEs is quite
tricky at times, and status check was one of quite unpleasant
experiences.
BTW git-diff won't work in situation when the directory was just
initialized and there were no commit. In that case added file = staged
file and it is possible to use git-ls-files.
Constantine
next prev parent reply other threads:[~2009-05-25 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 7:54 git-ls-files --added? Jon Seymour
2009-05-24 8:37 ` Jakub Narebski
2009-05-24 9:12 ` Jon Seymour
2009-05-24 18:17 ` Junio C Hamano
2009-05-25 6:33 ` Junio C Hamano
2009-05-25 7:31 ` Constantine Plotnikov [this message]
2009-05-25 7:46 ` Björn Steinbrink
2009-05-26 0:56 ` Jon Seymour
2009-05-29 21:26 ` David Aguilar
2009-05-29 22:01 ` Nanako Shiraishi
2009-05-29 23:06 ` Junio C Hamano
2009-05-30 6:02 ` David Aguilar
2009-05-31 16:19 ` Tony Finch
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=85647ef50905250031m375a14d9y252444a8bdc250b5@mail.gmail.com \
--to=constantine.plotnikov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jon.seymour@gmail.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).