[git-users] Re: Pissed at Git!

2010-06-01 Thread Trans
On Jun 1, 4:39 pm, Dan Preston danpres...@gmail.com wrote: You should be ok.  You can use the git reflog command to view the history of what you've had checked out.  You can then checkout the hash commit of your latest work again and create a branch from it.  Or alternatively you can merge

[git-users] Re: Pissed at Git!

2010-06-01 Thread Trans
Sorry, make that: $ git branch recentwork 8658a39 -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-us...@googlegroups.com. To unsubscribe from this group, send email to

Re: [git-users] Re: Pissed at Git!

2010-06-01 Thread Dan Preston
$ git branch recentwork 9c51d95 And I will have a branch at that point? Sorry, make that: $ git branch recentwork 8658a39 I can honestly never remember what order the branch name and hash go in so I tend to usually use the more longwinded approach. $ git checkout 8658a39 $ git checkout

[git-users] Re: Pissed at Git!

2010-06-01 Thread Konstantin Khomoutov
On Jun 2, 1:45 am, Dan Preston danpres...@gmail.com wrote: [...] Yeah, agreed.  It's not always immediately obvious.  It'll say Not currently on any branch. in the git commit message boilerplate as well as git status output though, so I try to keep my eyes peeled for that not being the branch

Re: [git-users] Re: Pissed at Git!

2010-06-01 Thread Dan Preston
Yes. Or `git tag recentwork 8658a39`. Or `git checkout master git merge 8658a39`. Everything Konstantin said is correct, but I just wanted to add that git tag will not get you out of the detached HEAD state, so you'll probably want to create a branch, or merge the hash into master directly,

Re: [git-users] Re: Pissed at Git!

2010-06-01 Thread Charles Manning
On Wednesday 02 June 2010 10:40:53 Konstantin Khomoutov wrote: Also, my idea was this: I found myself in situations like this one being discussed, and my first temptation after finding the relevant top commit in the reflog always was tag that immediately, then cool down, analyse the situation

[git-users] Re: Pissed at Git!

2010-06-01 Thread Jeffrey
I see. Well, it would be nice if it gave a little warning. I think I understand why it happened now though. I was tagging some old versions that I had failed to do in the past. Not exactly sure how but that must have been why. I believe the warnings about this have been getting more and more