Re: What's cooking in git.git (Dec 2012, #03; Wed, 12)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 13, 2012, 23:42 UTC
Message-ID: <7vsj79wmck.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAMP44s0qK6yNiPe0ERDJWK-wfm3DdXZYwRzisoCPJ7PjsdkObQ@mail.gmail.com>

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

Show 20 quoted lines

> On Thu, Dec 13, 2012 at 1:31 PM, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> One of the review points were about this piece in the test:
>>
>>     > +cmd=<<EOF
>>     > +import bzrlib
>>     > +bzrlib.initialize()
>>     > +import bzrlib.plugin
>>     > +bzrlib.plugin.load_plugins()
>>     > +import bzrlib.plugins.fastimport
>>     > +EOF
>>     > +if ! "$PYTHON_PATH" -c "$cmd"; then
>>
>>     I cannot see how this could have ever worked.
>>
>> And I still don't see how your "would work just fine" can be true.
>
> As I have explained, all this code is the equivalent of python -c '',
> or rather, it's a no-op. It works in the sense that it doesn't break
> anything.

Aren't you ashamed of yourself after having said this?

> The purpose of the code is to check for the fastimport plug-in, but
> that plug-in is not used any more, it's vestigial code, it doesn't
> matter if the check works or not, as long as it doesn't fail.

If so, the final version that is suitable for merging would have that unused code stripped away, no?

Show 6 quoted lines

>> But it is totally a different matter to merge a crap with known
>> breakage that is one easy fix away from the get-go.  Allowing that
>> means that all the times we spend on reviewing patches here go
>> wasted, discouraging reviewers.
>
> There is no breakage.

Unused code that burdens others to read through to make sure nothing is broken is already broken from maintenance point of view.

Why are you wasting my time and everybody's bandwidth on this, when you are very well capable of rerolling the series with removal and style fixes in far shorter time?