Re: [PATCH] remote-bzr: update old organization

From: Junio C Hamano <gitster@pobox.com>
Date: May 14, 2013, 22:14 UTC
Message-ID: <7vk3n1fbus.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vvc6lfc98.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 8 quoted lines

> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> And the clone would happen either way, with or without this patch,
>> because 'hg/origin/master' doesn't exist, the only purpose 'hg/origin'
>> serves is to block the new feature.
>
> That is the answer I was trying to extract out of you (I take the hg
> is a typo for bzr in the above, though).

Just to double check, I understand that the justification for removal is this:

     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.
    +repository. It is not used by 1.8.3, and did not host any useful
    +information in the code in 1.8.2.