Re: Document clone of clone loosing branches?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Vaclav Hanzl <hanzl@xxxxxxxxxxxxxxxxx> writes:

> I wander whether man git-clone is correct when it says "creates
> remote-tracking branches for each branch in the cloned repository".
> 
> IMHO remote-tracking branches in the original repository _are_
> branches and they are _not_ cloned (when using git-clone with no
> options) - maybe this is worth noting very explicitly?

It probably should read "for each _regular_ branch in the cloned
repository".

And of course if you are creating bare clone it does mirror regular
branches (1:1 mapping) instead of remote-tracking branches (mappping
from refs/heads/* into refs/remotes/origin/* namespace).

[...]
> Is it just my failure to read those few hundred man pages carefully
> enough (I did my best :-) ), or something worth fixing in man
> git-clone and tutorials?

Even if it is just your failure it would be worh correcting
(enhancing) documentation to make it more clear.

-- 
Jakub Narebski
Poland
ShadeHawk on #git
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux