From: Pratyush Yadav <me@yadavpratyush.com>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: Low prio: feature requests for git-gui
Date: Sun, 22 Dec 2019 23:17:18 +0530 [thread overview]
Message-ID: <20191222174718.nb3noztxo64g7jl3@yadavpratyush.com> (raw)
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
next prev parent reply other threads:[~2019-12-22 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 9:42 Low prio: feature requests for git-gui H.Merijn Brand
2019-12-22 17:47 ` Pratyush Yadav [this message]
2019-12-23 12:18 ` H.Merijn Brand
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=20191222174718.nb3noztxo64g7jl3@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=git@vger.kernel.org \
--cc=h.m.brand@xs4all.nl \
/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).