Project

General

Profile

Bug #5402

Misleading message by gitCheckout

Added by Gianluca Petrillo about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
02/10/2014
Due date:
% Done:

0%

Estimated time:
Duration:

Description

mrb gitCheckout usually tells that the HEAD version is being used, unless a version is specified, in which case it says nothing but the help hints otherwise.
In fact, we always land on develop branch by design and the help message misleads.
The text is possibly a debris from the SVN era...
Could you remove the message from the output and restore the one in the help message?

History

#1 Updated by Lynn Garren about 7 years ago

The message is correct. You land on the HEAD. For LArSoft git repositories, the HEAD is the develop branch, but for most other git repositories, the HEAD is the master branch. The git checkout actually does not know which you are getting, it only knows that it is checking out the HEAD. The definition of what HEAD means is internal to the specific repository.

#2 Updated by Gianluca Petrillo about 7 years ago

The message says "No version specified, using the head", with the suggestion that one could do otherwise.
So on my first time I looked at the help message of the script (`mrb gitCheckout -h`?).
From that, I thought that to get a specific version I should just do what the help says.
Now I know it could not work, but then I was completely mislead.

#3 Updated by Lynn Garren about 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Lynn Garren

If you had said that checking out a specific version does not work, you would be correct. That is now fixed and ready for the next release of mrb. However, you would normally not want to checkout a tag or branch by default. I have attempted to cleanup the messages as well.

#4 Updated by Lynn Garren about 7 years ago

  • Status changed from Assigned to Resolved

The fix is now available in mrb v0_05_07.

#5 Updated by Lynn Garren about 7 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF