git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/WIP] completion: complete git diff with only changed files.

From
Junio C Hamano <gitster@pobox.com>
Date
May 18, 2011, 20:00 UTC
Message-ID
<7voc2zbwz8.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DD3C814.8000100@gmx.de>
Paul Ebermann <Paul-Ebermann@gmx.de> writes:
> I'm normally using (for differences to head) git status first, and then
> have a look at the files I really want to see. Then completion of only
> the changed files seems useful.

By the time completion offers you the choices, you already have spent enough extra cycles to compute the paths, which is half the cost of generating the diff itself.

I have this nagging feeling that you are trying to solve a problem that does not exist. Perhaps you have too many things going on in your working tree at once, and if git helped in such a way that your workflow does not have to touch so many (possibly unrelated) things at once, you do not have to worry about unconstrained "git diff" output overwhelming you?

Previous: Paul EbermannNext: Paul Ebermann
Message 4 of 6 in “completion: complete git diff with only changed files.”
  1. completion: complete git diff with only changed files.Paul Ebermann, May 18, 2011
  2. Junio C HamanoMay 18, 2011
  3. Paul EbermannMay 18, 2011
  4. Junio C HamanoMay 18, 2011
  5. Paul EbermannMay 19, 2011
  6. Junio C HamanoMay 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.