From: Jakub Narebski <jnareb@gmail.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: christian.couder@gmail.com, t.gummerer@gmail.com,
git@vger.kernel.org, gitster@pobox.com,
Johannes.Schindelin@gmx.de
Subject: Re: [GSoC] Exploring Previous year Projects
Date: Wed, 29 Jan 2020 20:15:18 +0100 [thread overview]
Message-ID: <86k15ars55.fsf@gmail.com> (raw)
In-Reply-To: <20200129171248.6217-1-shouryashukla.oo@gmail.com> (Shourya Shukla's message of "Wed, 29 Jan 2020 22:42:48 +0530")
Shourya Shukla <shouryashukla.oo@gmail.com> writes:
> Hello,
>
> I was looking at the previous year projects[1] and a project intrigued me, namely:
> "Convert scripts to builtins".
>
> Following from Christian's advice[2], I have decided to focus on my project proposal.
> I noticed that various commands such as "git bisect", "git web--browse"(it particularly
> interests me) are still in their "shell" form and will be needed to be converted into
> their "C" form as per the project description.
[...]
> [1]: https://git.github.io/SoC-2019-Ideas/
> [2]: https://lore.kernel.org/git/CAP8UFD2Fo=2suQDLwzLM-Wg3ZzXpqHw-x0brPtPV0d4dRsgs9A@mail.gmail.com/
As far as I know, "git bisect" is currently being converted from shell
to C by Miriam Rubio for Outreachy project [3], so I am not sure if it
would be feasible as GSoC 2020 project.
I'm not sure if it would be possible and if it would make sense to
convert "git instaweb" and/or it's helper script "git web--browse" from
shell to C.
I think trying to convert either "git stash" or "git submodule" to C
would make more sense.
[3]: https://public-inbox.org/git/20200128144026.53128-1-mirucam@gmail.com/t/#u
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2020-01-29 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 17:12 [GSoC] Exploring Previous year Projects Shourya Shukla
2020-01-29 19:15 ` Jakub Narebski [this message]
2020-01-30 11:10 ` Converting scripted commands to built-ins, was " Johannes Schindelin
2020-01-30 15:14 ` Derrick Stolee
2020-01-31 9:32 ` Johannes Schindelin
2020-01-31 9:57 ` Johannes Schindelin
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=86k15ars55.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=shouryashukla.oo@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).