From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: git@vger.kernel.org
Subject: Re: Low prio: feature requests for git-gui
Date: Mon, 23 Dec 2019 13:18:49 +0100 [thread overview]
Message-ID: <20191223131849.13fc572e@pc09.procura.nl> (raw)
In-Reply-To: <20191222174718.nb3noztxo64g7jl3@yadavpratyush.com>
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
On Sun, 22 Dec 2019 23:17:18 +0530, Pratyush Yadav
<me@yadavpratyush.com> wrote:
> 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.
\o/
> > - 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.
I always interpreted Ctrl-J as to mean revert *all* changes. Now I know
better. Thanks.
If you add it to a context menu, I'd like to have an option in setting
not to get a dialog, as choosing it for a single file is (at least to
me) obvious enough not to need a dialog to confirm my choice.
> > - 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.
In my mind there is a difference between a changed file and a deleted
file. Ctrl-J restores the previous state, which in effect is the same
for both options.
> > - 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.
Yeah!
> > - 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.
Yeah! (again :)
> > Does this sound reasonable enough to make it a ticket/issue?
Thanks for the feedback
--
H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/
using perl5.00307 .. 5.31 porting perl5 on HP-UX, AIX, and Linux
https://useplaintext.email https://tux.nl http://www.test-smoke.org
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-23 12:19 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
2019-12-23 12:18 ` H.Merijn Brand [this message]
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=20191223131849.13fc572e@pc09.procura.nl \
--to=h.m.brand@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.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).