On 05/06/2014 08:40 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>
>> It would be pretty annoying to spend a lot of time fetching a big pack,
>> only to have the fetch fail because one reference out of many couldn't
>> be updated. This would force the user to download the entire pack
>>
Michael Haggerty writes:
> It would be pretty annoying to spend a lot of time fetching a big pack,
> only to have the fetch fail because one reference out of many couldn't
> be updated. This would force the user to download the entire pack
> again,...
Is that really true? Doesn't quickfetch op
On Mon, May 5, 2014 at 4:22 AM, Michael Haggerty wrote:
> On 04/22/2014 08:45 PM, Ronnie Sahlberg wrote:
>> This change is based on the previous ref transaction patches.
>> This is sent as a separate patch series since it implements a lot more
>> non-trivial changes to the behaviour than the previ
On 04/22/2014 08:45 PM, Ronnie Sahlberg wrote:
> This change is based on the previous ref transaction patches.
> This is sent as a separate patch series since it implements a lot more
> non-trivial changes to the behaviour than the previous patches and thus can
> use more detailed review.
>
> Upda
This change is based on the previous ref transaction patches.
This is sent as a separate patch series since it implements a lot more
non-trivial changes to the behaviour than the previous patches and thus can
use more detailed review.
Update fetch.c to use ref transactions when performing updates.
5 matches
Mail list logo