Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-18 Thread Jonathan Tan
On Thu, 18 Jan 2018 09:56:50 +0100 Christian Couder wrote: > I am still not very happy with fetch_object() not returning anything. > I wonder what happens when that function is used to fetch from a repo > that cannot provide the requested object. My idea was to save

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-18 Thread Christian Couder
On Wed, Jan 10, 2018 at 11:03 PM, Jeff Hostetler wrote: > > > On 1/10/2018 2:57 PM, Junio C Hamano wrote: >> >> Jeff Hostetler writes: >> >>> On 1/9/2018 6:33 PM, Junio C Hamano wrote: --

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-10 Thread Jeff Hostetler
On 1/10/2018 2:57 PM, Junio C Hamano wrote: Jeff Hostetler writes: On 1/9/2018 6:33 PM, Junio C Hamano wrote: -- [Cooking] * jh/fsck-promisors (2017-12-08) 10 commits [...] * jh/partial-clone (2017-12-08) 13

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-10 Thread Junio C Hamano
Ævar Arnfjörð Bjarmason writes: > On Tue, Jan 09 2018, Junio C. Hamano jotted: > >> * ab/wildmatch-tests (2018-01-04) 7 commits >> (merged to 'next' on 2018-01-09 at 09f0b84098) >> + wildmatch test: create & test files on disk in addition to in-memory >> + wildmatch test:

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-10 Thread Junio C Hamano
Jeff Hostetler writes: > On 1/9/2018 6:33 PM, Junio C Hamano wrote: >> -- >> [Cooking] >> >> >> * jh/fsck-promisors (2017-12-08) 10 commits > [...] > >> * jh/partial-clone (2017-12-08) 13 commits > [...] > > Parts 2 and 3 of

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-10 Thread Jeff Hostetler
On 1/9/2018 6:33 PM, Junio C Hamano wrote: -- [Cooking] * jh/fsck-promisors (2017-12-08) 10 commits [...] * jh/partial-clone (2017-12-08) 13 commits [...] Parts 2 and 3 of partial clone have been simmering for a while now. I was wondering

Re: What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-09 Thread Ævar Arnfjörð Bjarmason
On Tue, Jan 09 2018, Junio C. Hamano jotted: > * ab/wildmatch-tests (2018-01-04) 7 commits > (merged to 'next' on 2018-01-09 at 09f0b84098) > + wildmatch test: create & test files on disk in addition to in-memory > + wildmatch test: perform all tests under all wildmatch() modes > +

What's cooking in git.git (Jan 2018, #02; Tue, 9)

2018-01-09 Thread Junio C Hamano
Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. You can find the changes