simont |
Wed 2014-07-30 10:45 |
Mmm. In fact I find myself thinking that since git commit -a modifies your index in a way that can wipe out carefully prepared stuff in it, you'd actually quite like it to have the side effect of leaving the prior index state somewhere easily recoverable, in cases where the index was modified.
Perhaps a handy approach would be for it to generate a second commit consisting of exactly what it would have done if you hadn't said -a , and pointed an ephemeral ref at it similar to FETCH_HEAD. Then you could trivially recover from an accidental -a by saying git reset NO_THE_OTHER_ONE , or some such. |
|