Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to
- From
Johannes Gilger <heipei@hackvalue.de>
- Date
- Jun 25, 2008, 05:29 UTC
- Message-ID
- <20080625052929.GA23079@dualtron.vpn.rwth-aachen.de>
- In-Reply-To
- <1214346098-24584-1-git-send-email-stevenrwalter@gmail.com>
On 24/06/08 18:21, Steven Walter wrote:
> Give "reset --hard" a -f (force) flag, without which it will refuse to > proceed if there are changes in the index or working tree.
Oh no. I can only agree and repeat myself, as I think this is nonsense. git is a tool, and like every tool you can hurt yourself with it if you don't read the manual and follow really simple guidelines. I used git reset --hard on a test-repo before using it on my real code, and it has never bit me since. Why do we have --hard then? It would be "An option which does nothing unless you also specify -f on the command-line".
Just my opinion, but I think quite a few people feel the same Regards, Jojo
-- Johannes Gilger <heipei@hackvalue.de> http://hackvalue.de/heipei/ GPG-Key: 0x42F6DE81 GPG-Fingerprint: BB49 F967 775E BB52 3A81 882C 58EE B178 42F6 DE81