From: Johannes Müller dersinndesleb...@gmx.net
I tried thinking of a way to prevent accidental deletion by git reset
--hard command, as I recently faced such a problem. How can you write a
wrapper replacing the command, so that it first does something like the
following? It should create a
Hi,
I can answer the question to why I ended up using reset at least, though
I can imagine more scenarios. I wanted to do a reset on the current
working directory (read subdirectory of the repository) instead of on
the whole repository, and assumed git would do as I intuitively expected
it to,
While reading your explanation I've imagined Bart Simpson writing Git
is always working on the whole index over and over on the desk:)
Sorry.
On Sun, Mar 16, 2014 at 2:35 PM, Johannes Müller
dersinndesleb...@gmx.net wrote:
Hi,
I can answer the question to why I ended up using reset at least,
Hi,
I tried thinking of a way to prevent accidental deletion by git reset
--hard command, as I recently faced such a problem. How can you write a
wrapper replacing the command, so that it first does something like the
following? It should create a new branch backup with all changes before
From: Johannes Müller dersinndesleb...@gmx.net
Hi,
I tried thinking of a way to prevent accidental deletion by git reset
--hard command, as I recently faced such a problem. How can you write
a
wrapper replacing the command, so that it first does something like
the
following? It should create
