From: Lars Schneider <larsxschneider@gmail.com>
Date: Sun, 21 May 2017 20:25:58 GMT
Subject: Re: [PATCH v3 4/4] convert: add "status=delayed" to filter process protocol
Message-ID: <7D282F93-6131-4A1E-BCFD-62EA9DDD7F9F@gmail.com>
In-Reply-To: <48d9e7f0-15bf-ce0e-aae8-4c3ebd5c07cf@web.de>


> On 19 Apr 2017, at 20:55, Torsten Bögershausen <tboegi@web.de> wrote:
> 
> 
>>> (Back to the roots)
>>> Which criteria do you have in mind: When should a filter process the blob
>>> and return it immediately, and when would it respond "delayed" ?
>> 
>> See above: it's up to the filter. In case of Git LFS: delay if a network call is required.
>> 
> That make sense.
> I try to understand the big picture, and from here try to review
> the details.
> Does it make sense to mention "git lfs" in the commit message,
> and/or add some test code ?

I'll mention Git LFS in the commit message. The test code (t/t0021/rot13-filter.pl)
should mimic the behavior of Git LFS already.

Thanks,
Lars