git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
	Olga Telezhnaya <olyatelezhnaya@gmail.com>,
	Thomas Gummerer <t.gummerer@gmail.com>,
	Elijah Newren <newren@gmail.com>,
	Rohit Ashiwal <rohit.ashiwal265@gmail.com>
Subject: Re: [GSoC] My project blog
Date: Tue, 20 Aug 2019 19:41:34 -0300	[thread overview]
Message-ID: <CAHd-oW6j1-XuPA8XcwmBKhuAeGMEB23NMd1h1KDmn_Z+VJpu1w@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD2NEM2YWfKr2hz2vs-xBZ0qo96QbdyMDUu7PePm7RnfRw@mail.gmail.com>

On Tue, Aug 20, 2019 at 9:16 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> 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 :)

> > 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!

> > 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

  reply	other threads:[~2019-08-20 22:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  4:34 [GSoC] My project blog Matheus Tavares Bernardino
2019-07-14  7:38 ` Matheus Tavares Bernardino
2019-07-14 11:00   ` Christian Couder
2019-07-14 16:38     ` Matheus Tavares Bernardino
2019-07-23  1:13 ` Matheus Tavares Bernardino
2019-07-29 20:41 ` Matheus Tavares Bernardino
2019-08-06  2:54 ` Matheus Tavares Bernardino
2019-08-06  7:16   ` Christian Couder
2019-08-08 14:22     ` Matheus Tavares Bernardino
2019-08-13  4:06 ` Matheus Tavares Bernardino
2019-08-13 10:51   ` Christian Couder
2019-08-20  4:58 ` Matheus Tavares Bernardino
2019-08-20 11:27   ` Olga Telezhnaya
2019-08-20 12:16     ` Christian Couder
2019-08-20 22:41       ` Matheus Tavares Bernardino [this message]
2019-08-27  3:03 ` Matheus Tavares Bernardino

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=CAHd-oW6j1-XuPA8XcwmBKhuAeGMEB23NMd1h1KDmn_Z+VJpu1w@mail.gmail.com \
    --to=matheus.bernardino@usp.br \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=olyatelezhnaya@gmail.com \
    --cc=rohit.ashiwal265@gmail.com \
    --cc=t.gummerer@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).