From: Elijah Newren <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: Git Mailing List <firstname.lastname@example.org>, Jeff King <email@example.com> Subject: Re: What's cooking in git.git (Nov 2020, #02; Mon, 9) Date: Mon, 9 Nov 2020 16:44:17 -0800 [thread overview] Message-ID: <CABPp-BGtO5bgoinmjc3=WwW+w7G4Js14iGvO_qQ6oF3EcQt7xQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Nov 9, 2020 at 3:45 PM Junio C Hamano <email@example.com> wrote: > > * en/strmap (2020-11-06) 15 commits > - shortlog: use strset from strmap.h > - Use new HASHMAP_INIT macro to simplify hashmap initialization > - strmap: take advantage of FLEXPTR_ALLOC_STR when relevant > - strmap: enable allocations to come from a mem_pool > - strmap: add a strset sub-type > - strmap: split create_entry() out of strmap_put() > - strmap: add functions facilitating use as a string->int map > - strmap: enable faster clearing and reusing of strmaps > - strmap: add more utility functions > - strmap: new utility functions > - hashmap: provide deallocation function names > - hashmap: introduce a new hashmap_partial_clear() > - hashmap: allow re-use after hashmap_free() > - hashmap: adjust spacing to fix argument alignment > - hashmap: add usage documentation explaining hashmap_free[_entries]() > (this branch is used by en/merge-ort-impl.) > > A speciailization of hashmap that uses a string as key has been > introduced. Hopefully it will see wider use over time. > > Will merge to 'next'? Yes, please. Peff went over the series in detail and said it looked good to him as of v4 (he also seemed fine with the extra change in v5 that I made in response to your request). I'm not aware of any issues or further requests, and believe it is done. I'll CC Peff just in case he wants to change his mind and request any more changes here... However, you have an extra 'i' in your spelling of 'specialization' when describing this series. You might want to fix that when merging to next.
next prev parent reply other threads:[~2020-11-10 0:44 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-09 23:42 Junio C Hamano 2020-11-10 0:44 ` Elijah Newren [this message] 2020-11-10 1:03 ` Jeff King 2020-11-10 13:31 ` ds/maintenance-part-3 (was Re: What's cooking in git.git (Nov 2020, #02; Mon, 9)) Derrick Stolee 2020-11-16 23:56 ` Emily Shaffer 2020-11-17 0:40 ` Junio C Hamano 2020-11-17 1:07 ` Emily Shaffer 2020-11-17 13:56 ` Derrick Stolee 2020-11-17 19:18 ` Emily Shaffer 2020-11-17 19:34 ` Junio C Hamano 2020-11-17 21:12 ` Derrick Stolee 2020-11-19 2:16 ` Junio C Hamano 2020-11-19 13:25 ` Derrick Stolee 2020-11-19 15:53 ` Derrick Stolee 2020-11-19 18:06 ` Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CABPp-BGtO5bgoinmjc3=WwW+w7G4Js14iGvO_qQ6oF3EcQt7xQ@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: What'\''s cooking in git.git (Nov 2020, #02; Mon, 9)' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).