Re: git bug/feature request

From: Alex Riesen <raa.lkml@gmail.com>
Date: Nov 27, 2007, 13:03 UTC
Message-ID: <81b0412b0711270503s7e69be3bn151cfa58b8067f35@mail.gmail.com>
In-Reply-To: <200711271231.51270.gapon007@gmail.com>

On 27/11/2007, gapon <gapon007@gmail.com> wrote:

Show 6 quoted lines

> as i wrote in my first email - i know that this is not "correct" scenario (i
> don't and won't use it anywhere) - but the git's behaviour is in such case
> confusing, at least for me
> just for clarification - my email wasn't about how to push or create shared
> repository - it was just about what i have discovered while playing with
> different scms

Well... It is known problem, for one. That user B of yours, did he just cloned user A's repo?

What I suspect is a change in how git-clone setups the cloned repo could have taken care of it. We could either setup push-configuration so that it just does not work (and let user change to his preference), or somehow figure out where the pushed references can safely land and put that in the cloned repo configuration (that is "SOMEHOW", I afraid. Absolutely no idea what could that be).