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

Re: [GSoC] My project blog

From
Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Date
Aug 20, 2019, 22:41 UTC
Message-ID
<CAHd-oW6j1-XuPA8XcwmBKhuAeGMEB23NMd1h1KDmn_Z+VJpu1w@mail.gmail.com>
In-Reply-To
<CAP8UFD2NEM2YWfKr2hz2vs-xBZ0qo96QbdyMDUu7PePm7RnfRw@mail.gmail.com>

On Tue, Aug 20, 2019 at 9:16 AM Christian Couder <christian.couder@gmail.com> wrote:

Show 18 quoted lines
>
> Hi Matheus,
>
> On Tue, Aug 20, 2019 at 1:28 PM Olga Telezhnaya
> <olyatelezhnaya@gmail.com> wrote:
> >
> > вт, 20 авг. 2019 г. в 07:59, Matheus Tavares Bernardino
> > <matheus.bernardino@usp.br>:
> > >
> > > I just posted the penultimate report on my project:
> > > https://matheustavares.gitlab.io/posts/going-for-a-too-big-step This
> > > week I’ve been working on a v2 of threaded git-grep w/ parallel
> > > inflation, to allow threads when grepping submodules. I also tried
> > > some more optimizations along the way.
> >
> > Thank you for great blog post! You have done so many things, it is impressive.
>
> Yeah, great blog post again!
Thank you both for the always encouraging comments :)
Show 8 quoted lines
> > I absolutely agree with your plans to structure the job and split it
> > to smaller pieces, it should definitely help. Moreover, if you want,
> > you can make something like a documentation and delegate some parts.
>
> I also agree with the above. I think it would be really nice for
> example if we could have something in Documentation/technical/
> describing how multi-threading in `git grep` works and how it could be
> improved. (You can of course copy paste from your blog.)

Hm, good idea! I would have to revisit the important points and better formulate them, but that could hopefully help in future optimizations to git-grep.

> About static function-scope variables I wonder if we could have one
> day some .h and .c files with only thread safe functions in them.

Yes, that would probably require quite some work but would definitely be very helpful!

Show 6 quoted lines
> > I hope you enjoyed this summer :) Thank you for your readiness to
> > continue contributing after GSoC. It is not mandatory, you do not have
> > to finish the project, but if you want - all the community will be so
> > glad to see you as the contributor.
>
> Thank you for your work and for considering continuing after the GSoC,

Thank you both, again. It's been a great summer of code! (although it's winter here haha) I do hope to finish the project and keep contributing with whatever I can :)

Best, Matheus

Previous: Christian CouderNext: Matheus Tavares Bernardino
Message 15 of 16 in “[GSoC] My project blog”
  1. Matheus Tavares BernardinoJul 3, 2019
  2. Matheus Tavares BernardinoJul 14, 2019
  3. Christian CouderJul 14, 2019
  4. Matheus Tavares BernardinoJul 14, 2019
  5. Matheus Tavares BernardinoJul 23, 2019
  6. Matheus Tavares BernardinoJul 29, 2019
  7. Matheus Tavares BernardinoAug 6, 2019
  8. Christian CouderAug 6, 2019
  9. Matheus Tavares BernardinoAug 8, 2019
  10. Matheus Tavares BernardinoAug 13, 2019
  11. Christian CouderAug 13, 2019
  12. Matheus Tavares BernardinoAug 20, 2019
  13. Olga TelezhnayaAug 20, 2019
  14. Christian CouderAug 20, 2019
  15. Matheus Tavares BernardinoAug 20, 2019
  16. Matheus Tavares BernardinoAug 27, 2019

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.