Am 23.12.2016 um 20:49 schrieb John Hendy:
Sure... I get that that I *can* do that. I just wondered why I
*needed* to do that.
When you are in a "detached HEAD" situation, you will always have to
tell git explicitly to switch to some other commit (most likely a
branch). Git pull works with
On Fri, Dec 23, 2016 at 5:24 AM, Achim Gratz wrote:
> Am 22.12.2016 um 17:44 schrieb John Hendy:
>>
>> $ git pull
>> From http://orgmode.org/org-mode
>>13751c3249..820d1eb617 maint -> origin/maint
>>7fd61c4f92..1c89082600 master -> origin/master
>> You are
Am 22.12.2016 um 17:44 schrieb John Hendy:
$ git pull
From http://orgmode.org/org-mode
13751c3249..820d1eb617 maint -> origin/maint
7fd61c4f92..1c89082600 master -> origin/master
You are not currently on a branch.
Well, then you want to do a
git checkout master
or
git
I've not encountered this issue before, but on a git pull last night I
was greeted with a message like this (I don't have the original which
listed several other branches):
$ git pull
>From http://orgmode.org/org-mode
13751c3249..820d1eb617 maint -> origin/maint
7fd61c4f92..1c89082600