On Tue, May 14, 2013 at 12:30 PM, Junio C Hamano <gits...@pobox.com> wrote:
> Felipe Contreras <felipe.contre...@gmail.com> writes:
>> If a clone exists with the old organization (v1.8.2) it will prevent the
>> new shared repository organization from working, so let's remove this
>> repository, which is not used any more.
>> Signed-off-by: Felipe Contreras <felipe.contre...@gmail.com>
> What happens with and without this patch to an existing user from
> 1.8.2 days, when she does what?
I already explained it would prevent the new shared repository
organization from working, so the old organization would be used; the
repositories won't be shared.
> A sample answer (to show the level of descriptiveness, not the
> content, I am epecting) might go something like "Because the
> organization is different, it will barf whenever she tries to
> incrementally update from the other side. By removing the old one
> 1.8.3 contrib/ does not understand, at least we can unstuck her; she
> ends up reimporting the whole history, though."
Bazaar won't barf, the repositories will be duplicated, so the shared
feature won't work.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html