Petr Baudis <pasky@xxxxxxx> writes:
> and --use-immingled-remote can be used to get the original behaviour;
> it is also implied by --bare.
What's immingled?
> We get confused, frustrated and data-losing users *daily* on #git now
> because git-clone still produces the crippled repositories having the
> remote and local heads freely mixed together.
>
> Signed-off-by: Petr Baudis <pasky@xxxxxxx>
Being strongly opinionated, not giving enough credit for the
evolutionary process behind the history and venting frustration
in the proposed commit log message is never a good strategy to
get the patch applied.
Even though I fully agree that use-separate-remotes should be
the default, to the point that I do not think we do not even
need a backward compatibility option. People who want to use
traditional layout for simple one-remote-branch-only project
would not suffer anyway because 'origin' still means origin in
the new layout (refs/remotes/origin/HEAD).
We would need to update the tutorials to match this,though. I
think it talks about the traditional layout and say 'See, now
you can run "ls .git/refs/heads/{master,origin}"' or something
like that.
-
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