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

Re: Git in Outreachy?

From
Shourya Shukla <shouryashukla.oo@gmail.com>
Date
Sep 21, 2020, 20:56 UTC
Message-ID
<CAP6+3T11vpwgJJZQwTC6vgp2+RzRS8fxLLyZrbFvt3=cmi8vyA@mail.gmail.com>
In-Reply-To
<CAP8UFD05qPn6kGRTQGhwABvZbfoH3xcK3VpFo7d5koj9d7mUsg@mail.gmail.com>

On Mon, Sep 21, 2020 at 9:52 AM Christian Couder <christian.couder@gmail.com> wrote:

Show 23 quoted lines
>
> 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 would appreciate help to find project ideas though. Are there still
> > >> scripts that are worth converting to C (excluding git-bisect.sh and
> > >> git-submodule.sh that are still worked on)?
> > >
> > > I think Dscho's e-mail linked below gives a nice overview of the various
> > > scripts and their likely status as of Jan2020:
> > >
> > > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/
> > >
> > > 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, I am a bit busy right now catching up with the classes and assignments in my college. I will try to deliver a follow-up v2 to 'submodule add' in a couple of weeks.

Show 37 quoted lines
> > 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.
>
> > - 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.

If we are talking about submodules, then one project can be to improve the parsing of 'submodule--helper.c' and try to eliminate the shell scripting for this purpose. Another thing which can be done is to clean up the helper sub-commands which were created to aid the conversion (iff they are of little to no use now). I do not have an exact idea if the "improve parsing" and conversion of a couple of subcommands* will be a project big enough for Outreachy or not though.

*'submodule update' is a bit messed up right now and will need a solid conversion to C since some of its fragments are there in the C code while some aren't. Also, the shell code of this subcommand is still there meaning that the fragments do not play any direct role in the functioning of the subcommand. I can pass on the conversion of 'update' to Outreachy if the addition of this will amount to a complete project for a potential Outreachy intern.

Regards, Shourya Shukla

Previous: Kaartic Sivaraam
Message 44 of 44 in “Git in Outreachy?”
  1. Jeff KingAug 28, 2020
  2. Christian CouderAug 31, 2020
  3. Jonathan NiederSep 3, 2020
  4. Philip OakleySep 4, 2020
  5. Johannes SchindelinSep 7, 2020
  6. Philip OakleySep 16, 2020
  7. Johannes SchindelinSep 16, 2020
  8. Philip OakleySep 17, 2020
  9. Taylor BlauSep 9, 2020
  10. Jonathan NiederSep 10, 2020
  11. Taylor BlauSep 10, 2020
  12. Christian CouderSep 16, 2020
  13. Christian CouderSep 16, 2020
  14. Junio C HamanoAug 31, 2020
  15. Emily ShafferAug 31, 2020
  16. Jeff KingSep 1, 2020
  17. Jeff KingSep 3, 2020
  18. Jeff KingSep 15, 2020
  19. Kaartic SivaraamSep 15, 2020
  20. Jeff KingSep 15, 2020
  21. Christian CouderSep 19, 2020
  22. Phillip WoodSep 19, 2020
  23. Christian CouderSep 16, 2020
  24. Johannes SchindelinSep 2, 2020
  25. Christian CouderSep 16, 2020
  26. Phillip WoodSep 16, 2020
  27. Christian CouderSep 17, 2020
  28. Phillip WoodSep 17, 2020
  29. Christian CouderSep 18, 2020
  30. Elijah NewrenSep 17, 2020
  31. Christian CouderSep 18, 2020
  32. Kaartic SivaraamSep 27, 2020
  33. Christian CouderSep 27, 2020
  34. Christian CouderOct 29, 2020
  35. Kaartic SivaraamSep 6, 2020
  36. Johannes SchindelinSep 7, 2020
  37. Christian CouderSep 16, 2020
  38. Johannes SchindelinSep 16, 2020
  39. Christian CouderSep 19, 2020
  40. Johannes SchindelinSep 20, 2020
  41. Kaartic SivaraamSep 20, 2020
  42. Christian CouderSep 21, 2020
  43. Kaartic SivaraamSep 21, 2020
  44. Shourya ShuklaSep 21, 2020

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.