On Wed, Nov 16, 2022 at 03:55:54PM +0400, Konstantin Khomoutov wrote:
[...]
> Basically, that's the reason why all branches of a cloned repo become remote
> branches in your local repo: because Git cannot read your mind and somehow
> infrer which model you're about to implement about working with branches here.
[...]
Another perspective regarding branches using a real-world example: in the
local clone of a Git repository containing the project I'm working on at my
$dayjob, there's currently 190+ remote branches - and this is even though I
fetch from our central Git repo using the command `git fetch --prune origin`
which deletes remote branches that are gone in the source repository. And I
have only 8 local ("my own") branches.
I surely would not want all those 190 branches live in "my own" space in the
repository - that'd just been too much of a cognitive burden which would
require me to invent certain workarounds.
The key takeaway I'd propose is that once you consider using an SCM at a scale
beyond certain threshold, you start looking at the tool's design at different
angles.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/20221117092046.edoajnyaqwghzxun%40carbon.
