Derrick Stolee writes:
> On 10/15/2019 3:11 AM, Eric Wong wrote:
>> Junio C Hamano wrote:
>>> Eric Wong writes:
>>>
I just took a brief look, but that appears to leak memory.
"hashmap_free(var, 1)" should be replaced with
"hashmap_free_entries(var, struct foo, member)"
On 10/15/2019 3:11 AM, Eric Wong wrote:
> Junio C Hamano wrote:
>> Eric Wong writes:
>>
>>> I just took a brief look, but that appears to leak memory.
>>>
>>> "hashmap_free(var, 1)" should be replaced with
>>> "hashmap_free_entries(var, struct foo, member)"
>>>
>>> Only "hashmap_free(var, 0)" can
Junio C Hamano wrote:
> Eric Wong writes:
>
> > I just took a brief look, but that appears to leak memory.
> >
> > "hashmap_free(var, 1)" should be replaced with
> > "hashmap_free_entries(var, struct foo, member)"
> >
> > Only "hashmap_free(var, 0)" can become "hashmap_free(var)"
>
> I delibera
Eric Wong writes:
> I just took a brief look, but that appears to leak memory.
>
> "hashmap_free(var, 1)" should be replaced with
> "hashmap_free_entries(var, struct foo, member)"
>
> Only "hashmap_free(var, 0)" can become "hashmap_free(var)"
I deliberately avoided merge-time band-aid fixups on
Johannes Schindelin wrote:
> On Fri, 11 Oct 2019, Junio C Hamano wrote:
> > * ds/sparse-cone (2019-10-08) 17 commits
> > - sparse-checkout: cone mode should not interact with .gitignore
> > - sparse-checkout: write using lockfile
> > - sparse-checkout: update working directory in-process
> > -
Hi Junio,
On Fri, 11 Oct 2019, Junio C Hamano wrote:
> * ds/sparse-cone (2019-10-08) 17 commits
> - sparse-checkout: cone mode should not interact with .gitignore
> - sparse-checkout: write using lockfile
> - sparse-checkout: update working directory in-process
> - sparse-checkout: sanitize f
Junio C Hamano writes:
> By the way, I think I made a mistake in my calendar math.
>
> This topic was merged to 'next' on the 7th and it is not especially
> tricky; unless I (or somebody else) find glaring issues in it during
> the final sanity check before merging it to 'master' during the next
Elijah Newren writes:
> Did I shoot myself in the foot by being quick to jump on Rene's couple
> of cosmetic touch-up suggestions he posted over a week after the
> series was originally posted?
If the suggested updates were simple enough to do and would improve
the result sufficiently (which is
On Fri, Oct 11, 2019 at 9:42 AM Junio C Hamano wrote:
>
> Elijah Newren writes:
>
> >> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> >> (merged to 'next' on 2019-10-07 at 3e75779e10)
> >> + fast-export: handle nested tags
> >> ...
> >> + fast-export: fix exporting a tag and nothing
Elijah Newren writes:
>> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
>> (merged to 'next' on 2019-10-07 at 3e75779e10)
>> + fast-export: handle nested tags
>> ...
>> + fast-export: fix exporting a tag and nothing else
>>
>> Updates to fast-import/export.
>>
>> Will merge to 'mast
On Fri, Oct 11, 2019 at 12:35 AM Junio C Hamano wrote:
> [Cooking]
[...]
> * en/fast-imexport-nested-tags (2019-10-04) 8 commits
> (merged to 'next' on 2019-10-07 at 3e75779e10)
> + fast-export: handle nested tags
> + t9350: add tests for tags of things other than a commit
> + fast-export:
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.
We may want to merge down fixes ac
12 matches
Mail list logo