On Fri, Aug 16, 2013 at 04:21:59PM +0200, Saša Tomić wrote:
> git commit ==> git reset --soft HEAD^
The commit does still exists, you can find it in the reflog. This is
important if you for example commits a huge file and wants to remove it.
That commit needs to be gc:ed too, and this is dangerous.
On Fri, Aug 16, 2013 at 3:26 PM, Jeff King wrote:
> On Fri, Aug 16, 2013 at 10:55:06AM +0200, Saša Tomić wrote:
>
>> it just occurred to me -- the command that I would REALLY like to have
>> is simple:
>>
>> git undo
>>
>> which 'undo'es the last action that has not been pushed yet --
>> whichev
On Fri, Aug 16, 2013 at 10:55:06AM +0200, Saša Tomić wrote:
> it just occurred to me -- the command that I would REALLY like to have
> is simple:
>
> git undo
>
> which 'undo'es the last action that has not been pushed yet --
> whichever the action is. Similarly to the 'back' button in the
> b
Hi to all,
I've been using git for some time now, but I'm in no way a git expert.
I typically hack my way through the variety of commands that git
provides. I believe that most git users work similarly.
it just occurred to me -- the command that I would REALLY like to have
is simple:
git undo
4 matches
Mail list logo