A public Git repository was cloned to local storage. The repository is for MSM SoC Linux kernel development.
git remote show origin
generates a long list of tracked remote branches. Here an example of one list item
caf/linaro/linux-linaro-stable/v3.14/topic/arm64-apm tracked
Question 1
What type of stuff does the element topic refer to?
What type of stuff does the element v3.14 refer to?
What type of stuff does the element linux-linaro-stable refer to?
What type of stuff does the element linaro refer to?
What type of stuff does the element caf refer to?
I am not asking for the function the particular point might have in the addressed project. I am asking just for the type of the stuff/object.
Question 2 Why must the reference to the arm64-apm branch include all these elements? Why can't it be in the simple form
<remote name>/<branch name>
as learned from most Git books.
I believe the slashes you see in caf/linaro/linux-linaro-stable/v3.14/topic/arm64-apm tracked are just part of the branch name. To understand better, consider referring to the following remote tracking branch on your local Git setup:
git checkout -b origin/caf/linaro/linux-linaro-stable/v3.14/topic/arm64-apm tracked new_branch
Here, the first slash separates the remote (origin) from the rest of the branch name (caf/linaro/linux-linaro-stable/v3.14/topic/arm64-apm tracked).
We use BitBucket for our Git hosting, and branches with slashes in their name appear to be treated no differently than branches with no slashes. The slashes are just a convenient way to create a meaningful Git branch name. They may logically separate the branch name into different parts, but semantically they do not have any meaning.