Konstantin Khomoutov wrote:
> These branches are local to your repository. They are "remote" in the
> sense you're not supposed to modify them directly.
> So to inspect such a branch just use its full name ("origin/next" for
> instance) when working with commands like git-log.
>
> See [1], [2] for more info.
>
> Also your question appears to be quite basic which hints at that you did
> not read a good book on Git before using it. So starting at [3] is
> recommended -- it mentions a bunch of good books and manuals
Pointing to good references is a valuable thing --- thank you for that.
But I also want to point out that if you need to read a book before Git
becomes usable then we are doing something wrong. :)
In this example, perhaps the "git branch" manual page needs some
improvement?
Jonathan Nieder (2):
Documentation/branch: split description into subsections
Documentation/branch: briefly explain what a branch is
Documentation/git-branch.txt | 62 +++++++++++++++++++++++++-----------------
1 files changed, 37 insertions(+), 25 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html