From: Taylor Blau <me@ttaylorr.com>
To: Shubham Mishra <shivam828787@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSOC] Student Introduction - Reachability bitmap Improvements
Date: Sun, 20 Feb 2022 20:48:38 -0500 [thread overview]
Message-ID: <YhLvdjghyC+WQI6e@nand.local> (raw)
In-Reply-To: <CAC316V7M8bziK207tuFbctAqDdz+GC8OGaxM+B0earJtqDvBSg@mail.gmail.com>
Hi Shubham,
On Sun, Feb 20, 2022 at 10:39:13PM +0530, Shubham Mishra wrote:
> Hi,
> I am Interested in Project - "Reachability bitmap Improvements".
Great! I am excited that you are interested.
> I am going through the blog [1] and I love the technique we are using
> to fasten the queries. I have still not decided which one idea to pick
> out of many mentioned under "Reachability bitmap Improvements" but I
> think I will figure that out soon.
Let me know if you have any questions about the projects listed there,
and I'd be happy to add some more details. Alternatively, if none of
them pique your interest, that is OK, too, and we can brainstorm other
potential projects.
> Can someone please tell me if a micro-project - "avoid pipes in git
> related commands in test scripts" mentioned [2] is still available to
> take?
Oh, yes. Here is a command you can run to find some of them:
$ git grep "git[^|]*|\($\|[^|]\)" -- t
There are some false-positives, but that should give you a good starting
point to look for potential spots to touch up.
BTW, re-reading [2], I wanted to clarify that "The git command should be
on the left side of a pipe" is describing what we should remove, not
add.
I'm looking forward to your patches!
> [1] https://github.blog/2015-09-22-counting-objects
> [2] https://git.github.io/SoC-2022-Microprojects/
Thanks,
Taylor
next prev parent reply other threads:[~2022-02-21 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 17:09 [GSOC] Student Introduction - Reachability bitmap Improvements Shubham Mishra
2022-02-21 1:48 ` Taylor Blau [this message]
2022-02-22 7:47 ` Shubham Mishra
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YhLvdjghyC+WQI6e@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=shivam828787@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.
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 NNTP newsgroup(s).