Re: [PATCH v3 08/10] remote-hg: update bookmarks when pulling

From: Junio C Hamano <gitster@pobox.com>
Date: May 14, 2013, 22:25 UTC
Message-ID: <7vbo8dfbbr.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAMP44s0Wd4VEc_mwr=xguVAnXvn+YVz24u8eS4Nyy0HCjwJ+dw@mail.gmail.com>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 11 quoted lines

> On Tue, May 14, 2013 at 4:59 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> Without this fix, the user would never ever see new bookmarks, only the ones
>>> that (s)he initially cloned.
>>
>> Now, think again and realize how long it took you (the original
>> author) to discover issues and come up with these fixes and
>> explanation since the series was merged before -rc0.
>
> This issue has *always* been there, it's not a regression.

Then why are you rushing it?  -rc is a "regression-fix-only" period.

> Define "ready". It's probably more "ready" than any other bridge
> tool out there.

Anything that needs "oh, we need to push these ten patches to avoid regressions at the last minute" is not mature enough to be relied upon by end users for everyday use. That is what I meant.

But now you are saying these are not regression fixes, in which case they have to wait because the users have known about the limitations that existed for a long time and learned to live with them. That is a sign of mature (not "not ready") software.

You cannot be both.  Which is it?