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

Re: Low prio: feature requests for git-gui

From
Pratyush Yadav <me@yadavpratyush.com>
Date
Dec 22, 2019, 17:47 UTC
Message-ID
<20191222174718.nb3noztxo64g7jl3@yadavpratyush.com>
In-Reply-To
<20191220104258.1110d00e@pc09.procura.nl>
Hi Merijn,
On 20/12/19 10:42AM, H.Merijn Brand wrote:
> • Right click context menu on file-entry in Unstaged Changes list
It is something on my TODO list.
>   - Reset changes → git checkout this file
>     I see the current changes need to be reversed, are bogus or
>     invalid

I'm not sure what this means. When you hit Ctrl-J or choose it from the menu bar, current changes can be reverted by checking the file out from the index.

>   - Restore this file → git checkout this file
>     it was accidentally removed. Like the first option

What constitutes as "accidentally removed", and where do we restore the file from? If it needs to be restored from the index, then Ctrl-J should do the trick. If it needs to be restored from an older revision, well as of now git-gui doesn't have many features that deal with things like this. But maybe something like this can be added.

>   - Remove this file from disk
>     Somehow an invalid restore, a misplaced output or other reason
>     (core dump, debug output from other tools) made this file appear
>     and I don't want to add it to .gitignore

This feature was recently added in fa38ab6 (git-gui: revert untracked files by deleting them, 2019-12-01). You can hit Ctrl-J on the untracked file to delete it.

>   - Add to .gitignore
>     Like above, but this file will re-appear more often
A naive implementation of this shouldn't be too difficult. I'll see if I 
can find some time to do it.
 
> Does this sound reasonable enough to make it a ticket/issue?
-- 
Regards,
Pratyush Yadav
Previous: H.Merijn BrandNext: H.Merijn Brand
Message 2 of 3 in “Low prio: feature requests for git-gui”
  1. H.Merijn BrandDec 20, 2019
  2. Pratyush YadavDec 22, 2019
  3. H.Merijn BrandDec 23, 2019

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.