From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
Christian Couder <chriscool@tuxfamily.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>,
Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: Re: Git in Outreachy?
Date: Mon, 21 Sep 2020 13:29:19 +0530 [thread overview]
Message-ID: <8b189b7d-e43f-a6fd-ff43-a02bca9e4132@gmail.com> (raw)
In-Reply-To: <CAP8UFD05qPn6kGRTQGhwABvZbfoH3xcK3VpFo7d5koj9d7mUsg@mail.gmail.com>
On 21-09-2020 09:52, Christian Couder wrote:
> On Sun, Sep 20, 2020 at 6:31 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
>>
>> On 07-09-2020 00:26, Kaartic Sivaraam wrote:>
>>>
>>> I'm guessing only the status of submodule has changed as it's being
>>> worked on now.
>>
>> After giving it a second thought, I believe I should take back my word
>> about the git-submodule status changing. There still seems to be some
>> work left for it.
>
> Yeah, there is some work left, but Shourya said he was interested in
> continuing to work on it.
>
Yeah, he's most welcome to resume his work :)
>> To be clear,
>>
>> - there's 'add', whose conversion is currently stalled [1]
>
> Yeah, but it hasn't been stalled for a long time, and sometimes it
> takes time after the GSoC or Outreachy period for former GSoC students
> or Outreachy interns to resume their work.
>
Ok. Got it.
>> - there's 'update', which still has a decent amount of code [2]
>> in the shell script.
>> - we still have to complete the conversion completely converting
>> moving the rest of the bits from `git-submodule.sh` to C which is
>> mostly just the option parsing. This might be more trickier than
>> it sounds as we would've to ensure the we don't accidentally
>> change behaviour of the options when moving the option parsing to C.
>>
>> There's also an e-mail from Junio which is relevant [3]
>>
>> I'm not sure if this would be enough for a complete project on it's own.
>> I'm also not sure whether 'add' would get converted in the meantime. In
>> any case, I believe we could add a few other small refactoring projects
>> to make up for the rest of the period. For instance,
>>
>> - Replace more instances of `the_index` and `the_repository`
>> (https://github.com/gitgitgadget/git/issues/379)
>>
>> - Turn the `fetch_if_missing` global into a field of `struct repository`
>> (https://github.com/gitgitgadget/git/issues/251)
>>
>> - Possibly others from #leftoverbits
>>
>> Thoughts?
>
> Yeah, without 'add' we would have enough related issues for another
> project. I would prefer though that we wait for at least 3 months
> without any progress before suggesting them as a project. That's what
> we usually do and I think it's the right thing to do.
>
Ok. That makes sense. I also missed the fact that Shourya had also
expressed interested in converting the 'update' part of submodule in his
final GSoC report [A]. So, I agree that it's too early to propose the
rest of the submodule work for Outreachy.
Thanks.
References
===
[A]: https://shouryashukla.blogspot.com/2020/08/the-final-report.html
--
Sivaraam
next prev parent reply other threads:[~2020-09-21 8:00 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 6:56 Git in Outreachy? Jeff King
2020-08-31 6:55 ` Christian Couder
2020-09-03 6:00 ` Jonathan Nieder
2020-09-04 14:14 ` Philip Oakley
2020-09-07 18:49 ` Johannes Schindelin
2020-09-16 15:16 ` Philip Oakley
2020-09-16 18:43 ` Johannes Schindelin
2020-09-17 14:42 ` Philip Oakley
2020-09-09 18:26 ` Taylor Blau
2020-09-10 1:39 ` Jonathan Nieder
2020-09-10 2:19 ` Taylor Blau
2020-09-16 9:12 ` Christian Couder
2020-09-16 6:42 ` Christian Couder
2020-08-31 17:41 ` Junio C Hamano
2020-08-31 18:05 ` Emily Shaffer
2020-09-01 12:51 ` Jeff King
2020-09-03 5:41 ` Jeff King
2020-09-15 17:35 ` Jeff King
2020-09-15 17:55 ` Kaartic Sivaraam
2020-09-15 18:02 ` Jeff King
2020-09-19 8:12 ` Christian Couder
2020-09-19 15:10 ` Phillip Wood
2020-09-16 8:45 ` Christian Couder
2020-09-02 4:00 ` Johannes Schindelin
2020-09-16 9:01 ` Christian Couder
2020-09-16 9:45 ` Phillip Wood
2020-09-17 9:43 ` Christian Couder
2020-09-17 10:14 ` Phillip Wood
2020-09-18 8:37 ` Christian Couder
2020-09-17 15:34 ` Elijah Newren
2020-09-18 8:42 ` Christian Couder
2020-09-27 16:59 ` Kaartic Sivaraam
2020-09-27 21:16 ` Christian Couder
2020-10-29 10:13 ` Christian Couder
2020-09-06 18:56 ` Kaartic Sivaraam
2020-09-07 18:55 ` Johannes Schindelin
2020-09-16 9:35 ` Christian Couder
2020-09-16 20:27 ` Johannes Schindelin
2020-09-19 7:40 ` Christian Couder
2020-09-20 15:06 ` Johannes Schindelin
2020-09-20 16:31 ` Kaartic Sivaraam
2020-09-21 4:22 ` Christian Couder
2020-09-21 7:59 ` Kaartic Sivaraam [this message]
2020-09-21 20:56 ` Shourya Shukla
2021-09-03 2:40 Taylor Blau
2021-09-03 18:33 ` Emily Shaffer
2021-09-04 4:30 ` Christian Couder
2021-09-04 7:40 ` ZheNing Hu
2021-09-04 12:50 ` Jeff King
2021-09-05 8:58 ` ZheNing Hu
2021-09-06 12:36 ` Matheus Tavares Bernardino
2021-09-07 5:50 ` ZheNing Hu
2021-09-04 17:51 ` Taylor Blau
2021-09-18 16:10 ` Taylor Blau
2021-09-20 7:45 ` ZheNing Hu
2021-09-20 14:52 ` Christian Couder
2021-09-20 15:15 ` Christian Couder
2021-09-21 5:41 ` ZheNing Hu
2021-09-21 15:39 ` Christian Couder
2021-09-22 15:01 ` ZheNing Hu
2021-09-21 5:39 ` ZheNing Hu
2021-09-21 15:35 ` Christian Couder
2021-09-22 14:58 ` ZheNing Hu
2021-09-21 21:25 ` Taylor Blau
2021-09-29 14:18 ` Christian Couder
2021-09-29 17:34 ` Taylor Blau
2021-09-29 20:30 ` Taylor Blau
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=8b189b7d-e43f-a6fd-ff43-a02bca9e4132@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=shouryashukla.oo@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).