On Mon, Jul 18, 2022 at 07:16:28PM +0300, Konstantin Khomoutov wrote: [...]
> Another solution which seems logical at the first glance is using the "trash > bin" feature is the OS provides it but it also has practical problems: it is > never the core feature provided by the kernel, and Git is not always used by > human beings through graphical user interfaces, and also Git uses lots of > files not intended to be dealt with by the user anyway (though admittedly in > your particular case moving the files to the trash can could help). May be a good middle ground could be using the "trash can" facility _if possible_ with presenting a user with the summary of what unstaged files to be overwritten/removed. Still, implementing such mode is impossible in `git reset --hard` because it's being extensively used in scripts which must continue working unmodified. Adding a new command-line options forcing this work mode of the reset command to be extra-interactive will be of questionable utility as the user would have to type it in order to get this behavior. So, looks like it's a case for a new top-level command, I dunno. Adding new "sensible" top-level commands for already existing behavior is not uncommon: `git switch` is a good example. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20220718162812.6n2e4uwpsfrfvpk5%40carbon.
