Remove extra git describe on Rake shell install.

Created by: cirosantilli

I'm sure there is a good reason for this, but I'm just too curious to know why =)

IIUC:

• man gitrevisions says that refnames are already searched under refs/heads/<name> and then refs/remotes/<name> in that order by default. So saying git checkout branch will find remote/origin/branch already if heads/branch does not exist.
• no other type of revision name is stored under refs/heads/remote

cc @crohr you may have written that line, sorry if not.

Actually , what I really wanted to do is to remove the describe entirely: if I give a ref from the command line, it is simpler to use it directly instead of describe ref. People should never install the latest stable and always give the version that corresponds to their gitlab instance.

Created by: TeatroIO

I've prepared a stage. Click to open.

By Administrator on 2014-09-23T11:38:40 (imported from GitLab project)

By Administrator on 2014-09-23T11:38:40 (imported from GitLab)

Created by: crohr

@cirosantilli not sure why I put that. Probably because I wasn't sure of the behaviour. It's fine by me :)

By Administrator on 2014-09-23T16:25:28 (imported from GitLab project)

By Administrator on 2014-09-23T16:25:28 (imported from GitLab)

Created by: cirosantilli

@crohr @razer6 I read the manpages wrong: branchname will not match refs/remotes/origin/branchname, it will only match refs/remotes/branchname!

I got confused because git checkout does this extra search magically, but it fails for most other commands like reset and describe.

By Administrator on 2014-10-18T08:08:59 (imported from GitLab project)

By Administrator on 2014-10-18T08:08:59 (imported from GitLab)