git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Aug 2020, #07; Thu, 27)

From
Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Date
Aug 29, 2020, 04:28 UTC
Message-ID
<CAHd-oW75wy07jo+pZzqjkzYekMWVSp0DmEVNQLG8GyTPNLZ1bQ@mail.gmail.com>
In-Reply-To
<CABPp-BHCVWWFDL2kpWymNuX_t4anX2Xw-xiTK8N+MdrBoopERg@mail.gmail.com>
Hi, Elijah
On Thu, Aug 27, 2020 at 11:16 PM Elijah Newren <newren@gmail.com> wrote:
Show 22 quoted lines
>
> On Thu, Aug 27, 2020 at 2:46 PM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > * mt/grep-sparse-checkout (2020-06-12) 6 commits
> >  - config: add setting to ignore sparsity patterns in some cmds
> >  - grep: honor sparse checkout patterns
> >  - config: correctly read worktree configs in submodules
> >  - t/helper/test-config: facilitate addition of new cli options
> >  - t/helper/test-config: return exit codes consistently
> >  - doc: grep: unify info on configuration variables
> >
> >  "git grep" has been tweaked to be limited to the sparse checkout
> >  paths.
> >
> >  Review needed on 4/6; otherwise looking sane.
> >  cf. <CABPp-BGdEyEeajYZj_rdxp=MyEQdszuyjVTax=hhYj3fOtRQUQ@mail.gmail.com>
>
> Kinda disappointed to see this stalled out; especially after so much
> work put into it.  This spawned lots of other side discussions and a
> topic or two outside this series as well.  I really like the overall
> result we came up with out of this series and would like to see it
> land [...]

Yeah, I would also really like to see it land :) Thanks to your last rounds of review, I think we got to a much better design regarding each grep case.

Show 10 quoted lines
>  [...] If we can't get more reviewers, maybe we just merge it down
> anyway?  But, in an attempt to prod some review...
>
> Jonathan: I pinged you in chat about this series some time ago and you
> said you'd take a look and comment.  I can't find a reference
> anywhere, but maybe you talked with Matheus in IRC somewhere?  Do you
> recall?
>
> Matheus: Do you have any outstanding items for this series or is it
> good as far as you know?
Hm, I don't have anything else planned to add.

Just one minor aesthetic consideration: should we perhaps eliminate the sparse-checkout.c file (and the accompanying header) from the last patch? This file contains only one function; It was created with the idea of being later populated by another parallel series [1]. However, if we only have this function for now, should we move it elsewhere? I'm not sure where, though. Maybe to config.c, together with git_config_get_index_threads() and others?

[1]: https://lore.kernel.org/git/2188577cd848d7cee77f06f1ad2b181864e5e36d.1588857462.git.gitgitgadget@gmail.com/
Previous: Elijah NewrenNext: Derrick Stolee
Message 9 of 17 in “What's cooking in git.git (Aug 2020, #07; Thu, 27)”
  1. Junio C HamanoAug 27, 2020
  2. Jeff KingAug 27, 2020
  3. Junio C HamanoAug 27, 2020
  4. Taylor BlauAug 28, 2020
  5. Jeff KingAug 28, 2020
  6. Jeff KingAug 28, 2020
  7. Taylor BlauAug 28, 2020
  8. Elijah NewrenAug 28, 2020
  9. Matheus Tavares BernardinoAug 29, 2020
  10. ds/maintenance-part-[1-2] (was: What's cooking in git.git (Aug 2020, #07; Thu, 27))Derrick Stolee, Aug 28, 2020
  11. Hariom vermaAug 28, 2020
  12. Junio C HamanoAug 28, 2020
  13. Hariom vermaAug 29, 2020
  14. Hariom vermaAug 29, 2020
  15. Junio C HamanoAug 29, 2020
  16. Hariom vermaAug 29, 2020
  17. Junio C HamanoAug 29, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.