Re: [PATCH 3/4] config doc: elaborate on what transfer.fsckObjects does

From: Junio C Hamano <gitster@pobox.com>
Date: May 25, 2018, 03:22 UTC
Message-ID: <xmqq4liwpggs.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CAPig+cSd32O3ELaHxLD0_yRFmjMAo2k-jApopJmuEt7Z6W40-g@mail.gmail.com>

Eric Sunshine <sunshine@sunshineco.com> writes:

Show 11 quoted lines

>> +will instead be left unreferenced in the repository. That's considered
>> +a bug, and hopefully future git release will implement a quarantine
>> +for the "fetch" side as well.
>
> If this was a "BUGS" section in a man-page, the above might be less
> scary. In this context, however, I wonder if it makes sense to tone it
> down a bit:
>
>     On the fetch side, malformed objects will instead be left
>     unreferenced in the repository. (However, in the future, such
>     objects may be quarantined for "fetch", as well.)

I had an impression that nobody else sayd it is considered as a bug. Do we need to say it in this series? I'd rather not--with or without such a future modification (or lack of plan thereof), teaching the fetch side to pay attention to the various fsck tweaks is an improvement.