{"thread":{"id":"54148","subject":"Git in Outreachy?","startedAt":"2020-08-28T06:56:12Z","lastAt":"2020-10-29T10:13:45Z","messageCount":44,"participants":["Jeff King","Christian Couder","Junio C Hamano","Emily Shaffer","Johannes Schindelin","Jonathan Nieder","Philip Oakley","Kaartic Sivaraam","Taylor Blau","Phillip Wood","Elijah Newren","Shourya Shukla"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"404675","messageId":"20200828065609.GA2105118@coredump.intra.peff.net","threadId":"54148","inReplyTo":null,"subject":"Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-08-28T06:56:09Z","receivedAt":"2020-08-28T06:56:12Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"Are we interested in participating in the December 2020 round of\nOutreachy? The community application period is now open.\n\nI can look into lining up funding, but we'd also need:\n\n  - volunteers to act as mentors\n\n  - updates to our applicant materials (proposed projects, but also\n    microproject / patch suggestions)\n\n-Peff\n"},{"id":"404787","messageId":"CAP8UFD2rpNhDhyHdQNxS-KJZgcumsCpK_JQ5koCqXJd70s-+_w@mail.gmail.com","threadId":"54148","inReplyTo":"20200828065609.GA2105118@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-08-31T06:55:33Z","receivedAt":"2020-08-31T06:55:51Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Aug 28, 2020 at 8:56 AM Jeff King <peff@peff.net> wrote:\n>\n> Are we interested in participating in the December 2020 round of\n> Outreachy? The community application period is now open.\n\nI am interested in participating.\n\n> I can look into lining up funding, but we'd also need:\n>\n>   - volunteers to act as mentors\n\nI am interested in mentoring, but would prefer to co-mentor.\n\n>   - updates to our applicant materials (proposed projects, but also\n>     microproject / patch suggestions)\n\nIt looks like many micro-project ideas from GSoC 2020 are still valid,\nand I have a few new ones, so I am ok to create a micro-project page.\n\nI would appreciate help to find project ideas though. Are there still\nscripts that are worth converting to C (excluding git-bisect.sh and\ngit-submodule.sh that are still worked on)? Are there worthy\nrefactorings or improvements that we could propose as projects?\n"},{"id":"404821","messageId":"xmqqr1rmg1bf.fsf@gitster.c.googlers.com","threadId":"54148","inReplyTo":"20200828065609.GA2105118@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-08-31T17:41:40Z","receivedAt":"2020-08-31T17:41:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\n> Are we interested in participating in the December 2020 round of\n> Outreachy? The community application period is now open.\n>\n> I can look into lining up funding, but we'd also need:\n>\n>   - volunteers to act as mentors\n>\n>   - updates to our applicant materials (proposed projects, but also\n>     microproject / patch suggestions)\n>\n> -Peff\n\nFWIW, I am interested in seeing this project participating.  As\nusual, I won't be able to mentor to avoid biases, though.\n\nAs to microprojects, I think we saw #leftoverbits and #micrproject\nsprinkled in a handful of messages in recent discussions, so with\nthe help of list archive, we may come up with new ones.\n\nThanks.\n"},{"id":"404823","messageId":"20200831180537.GC331156@google.com","threadId":"54148","inReplyTo":"20200828065609.GA2105118@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Emily Shaffer","fromEmail":"emilyshaffer@google.com","sentAt":"2020-08-31T18:05:37Z","receivedAt":"2020-08-31T18:05:47Z","isPatch":false,"sender":{"key":"nasamuffin@google.com","avatar":"https://avatars.githubusercontent.com/u/1606826?v=4"},"body":"On Fri, Aug 28, 2020 at 02:56:09AM -0400, Jeff King wrote:\n> \n> Are we interested in participating in the December 2020 round of\n> Outreachy? The community application period is now open.\n> \n> I can look into lining up funding, but we'd also need:\n> \n>   - volunteers to act as mentors\n\nI'm interested in mentoring or co-mentoring this term. (I'm not working\nthis week but I didn't want to miss a deadline to volunteer.)\n\n> \n>   - updates to our applicant materials (proposed projects, but also\n>     microproject / patch suggestions)\n\nOne thought I had was whether it might be cool to shop for another\nco-mentor from Wireshark and have an intern teach Wireshark how to\ndecipher Git protocol. But it seems large, and maybe last-minute for\nthis term.\n\n - Emily\n"},{"id":"404858","messageId":"20200901125119.GA3250129@coredump.intra.peff.net","threadId":"54148","inReplyTo":"20200831180537.GC331156@google.com","subject":"Re: Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-09-01T12:51:19Z","receivedAt":"2020-09-01T12:52:36Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Aug 31, 2020 at 11:05:37AM -0700, Emily Shaffer wrote:\n\n> I'm interested in mentoring or co-mentoring this term. (I'm not working\n> this week but I didn't want to miss a deadline to volunteer.)\n\nOK, between you and Christian, then, it sounds like it's worth pursuing.\nI'll sign us up and try to arrange funding.\n\n> One thought I had was whether it might be cool to shop for another\n> co-mentor from Wireshark and have an intern teach Wireshark how to\n> decipher Git protocol. But it seems large, and maybe last-minute for\n> this term.\n\nThat sounds neat. I don't think it would be too large (in fact, I think\nit might end up being a bit small for a whole-term project). It would\ndefinitely require somebody from Wireshark being a co-mentor, though.\n\n-Peff\n"},{"id":"404912","messageId":"nycvar.QRO.7.76.6.2009020558550.56@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"20200828065609.GA2105118@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-02T04:00:55Z","receivedAt":"2020-09-02T08:50:43Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Peff,\n\nOn Fri, 28 Aug 2020, Jeff King wrote:\n\n> Are we interested in participating in the December 2020 round of\n> Outreachy? The community application period is now open.\n>\n> I can look into lining up funding, but we'd also need:\n>\n>   - volunteers to act as mentors\n>\n>   - updates to our applicant materials (proposed projects, but also\n>     microproject / patch suggestions)\n\nThank you for thinking of me! While I am eager to help, I think I won't be\nable to commit to a full term, though.\n\nAs to projects, I would like to believe that\nhttps://github.com/gitgitgadget/git/issues has grown into a useful\nresource.\n\nCiao,\nDscho\n"},{"id":"404954","messageId":"20200903054126.GA2053272@coredump.intra.peff.net","threadId":"54148","inReplyTo":"20200901125119.GA3250129@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-09-03T05:41:26Z","receivedAt":"2020-09-03T05:41:38Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Sep 01, 2020 at 08:51:20AM -0400, Jeff King wrote:\n\n> On Mon, Aug 31, 2020 at 11:05:37AM -0700, Emily Shaffer wrote:\n> \n> > I'm interested in mentoring or co-mentoring this term. (I'm not working\n> > this week but I didn't want to miss a deadline to volunteer.)\n> \n> OK, between you and Christian, then, it sounds like it's worth pursuing.\n> I'll sign us up and try to arrange funding.\n\nI'm still working out funding details, but in the meantime we're signed\nup. Potential mentors should propose projects here:\n\n  https://www.outreachy.org/communities/cfp/git/\n\nSooner is better than later. We can technically submit projects up until\nthe 24th, but student applications are open now, and have to be in by\nSeptember 20th.\n\n-Peff\n"},{"id":"404956","messageId":"20200903060041.GH4035286@google.com","threadId":"54148","inReplyTo":"CAP8UFD2rpNhDhyHdQNxS-KJZgcumsCpK_JQ5koCqXJd70s-+_w@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2020-09-03T06:00:41Z","receivedAt":"2020-09-03T06:00:49Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nChristian Couder wrote:\n\n> I would appreciate help to find project ideas though. Are there still\n> scripts that are worth converting to C (excluding git-bisect.sh and\n> git-submodule.sh that are still worked on)? Are there worthy\n> refactorings or improvements that we could propose as projects?\n\nI think setting up something like snowpatch[*] to run CI on patches\nthat have hit the mailing list but not yet hit \"seen\" might be a good\nproject for an interested applicant (and I'd be interested in\nco-mentoring if we find a taker).\n\nSome other topics that could be interesting:\n- better support for handling people's name changing\n- making signing features such as signed push easier to use (for\n  example by allowing signing with SSH keys to simplify PKI) and more\n  useful (for example by standardizing a way to publish signed push\n  logs in Git)\n- protocol: sharing notes and branch descriptions\n- formats: on-disk reverse idx\n- obliterate\n- cache server to take advantage of multiple promisors+packfile URIs\n\nJonathan\n\n[*] https://github.com/ruscur/snowpatch\n"},{"id":"405041","messageId":"a3613b9d-730a-7a4b-c84b-c833490fcea6@iee.email","threadId":"54148","inReplyTo":"20200903060041.GH4035286@google.com","subject":"Re: Git in Outreachy?","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-09-04T14:14:56Z","receivedAt":"2020-09-04T14:15:26Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"On 03/09/2020 07:00, Jonathan Nieder wrote:\n> Hi,\n>\n> Christian Couder wrote:\n>\n>> I would appreciate help to find project ideas though. Are there still\n>> scripts that are worth converting to C (excluding git-bisect.sh and\n>> git-submodule.sh that are still worked on)? Are there worthy\n>> refactorings or improvements that we could propose as projects?\n> I think setting up something like snowpatch[*] to run CI on patches\n> that have hit the mailing list but not yet hit \"seen\" might be a good\n> project for an interested applicant (and I'd be interested in\n> co-mentoring if we find a taker).\n>\n> Some other topics that could be interesting:\n> - better support for handling people's name changing\n> - making signing features such as signed push easier to use (for\n>   example by allowing signing with SSH keys to simplify PKI) and more\n>   useful (for example by standardizing a way to publish signed push\n>   logs in Git)\n> - protocol: sharing notes and branch descriptions\n> - formats: on-disk reverse idx\n> - obliterate\n> - cache server to take advantage of multiple promisors+packfile URIs\n>\n> Jonathan\n>\n> [*] https://github.com/ruscur/snowpatch\nA suggestion with high value for the Windows community\n- mechanism to map file names between the index and the local FS, should\na repos file/path name already be taken, or invalid. [1]\n\nPhilip\n\n[1]\nhttps://github.com/git-for-windows/git/issues/2803#issuecomment-687161483\n"},{"id":"405092","messageId":"441bd08b-ca7d-5977-a455-c4c2a4bd4bc9@gmail.com","threadId":"54148","inReplyTo":"20200828065609.GA2105118@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2020-09-06T18:56:33Z","receivedAt":"2020-09-06T18:57:20Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 28-08-2020 12:26, Jeff King wrote:\n> Are we interested in participating in the December 2020 round of\n> Outreachy? The community application period is now open.\n> \n> I can look into lining up funding, but we'd also need:\n> \n>   - volunteers to act as mentors\n>\n\nI'm willing to co-mentor a project for this term. I don't have any\nparticular preference of projects, though.\n\n> I would appreciate help to find project ideas though. Are there still\n> scripts that are worth converting to C (excluding git-bisect.sh and\n> git-submodule.sh that are still worked on)? \n\nI think Dscho's e-mail linked below gives a nice overview of the various\nscripts and their likely status as of Jan2020:\n\nhttps://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n\nI'm guessing only the status of submodule has changed as it's being\nworked on now.\n\n-- \nSivaraam\n"},{"id":"405133","messageId":"nycvar.QRO.7.76.6.2009060933480.56@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"a3613b9d-730a-7a4b-c84b-c833490fcea6@iee.email","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-07T18:49:11Z","receivedAt":"2020-09-07T18:49:26Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Philip,\n\nOn Fri, 4 Sep 2020, Philip Oakley wrote:\n\n> On 03/09/2020 07:00, Jonathan Nieder wrote:\n> >\n> > Christian Couder wrote:\n> >\n> >> I would appreciate help to find project ideas though. Are there still\n> >> scripts that are worth converting to C (excluding git-bisect.sh and\n> >> git-submodule.sh that are still worked on)? Are there worthy\n> >> refactorings or improvements that we could propose as projects?\n> > I think setting up something like snowpatch[*] to run CI on patches\n> > that have hit the mailing list but not yet hit \"seen\" might be a good\n> > project for an interested applicant (and I'd be interested in\n> > co-mentoring if we find a taker).\n> >\n> > Some other topics that could be interesting:\n> > - better support for handling people's name changing\n> > - making signing features such as signed push easier to use (for\n> >   example by allowing signing with SSH keys to simplify PKI) and more\n> >   useful (for example by standardizing a way to publish signed push\n> >   logs in Git)\n> > - protocol: sharing notes and branch descriptions\n> > - formats: on-disk reverse idx\n> > - obliterate\n> > - cache server to take advantage of multiple promisors+packfile URIs\n> >\n> > Jonathan\n> >\n> > [*] https://github.com/ruscur/snowpatch\n> A suggestion with high value for the Windows community\n> - mechanism to map file names between the index and the local FS, should\n> a repos file/path name already be taken, or invalid. [1]\n\nThis suggestion keeps coming up, but I cannot help but highly doubt that\nit will prove useful in practice: if your source code contains a file\ncalled `aux.c`, chances are that your build system lists this file\nspecifically, and it won't do at all to \"magically\" rename it to, say,\n`aux_.c` during checkout.\n\nIn contrast, I think a much more useful project would be to relax the\n`core.protectNTFS` protections to cover only the files that will be\nwritten to disk, and not bother even checking the files excluded from a\nsparse-checkout for invalid file names on NTFS.\n\nThis is trickier, of course, than meets the eye: we would still want to be\n_very_ careful to ensure that the unchecked file names will _never_ make\nit to the disk. And, slightly related, the question whether checking for\n`.git` (or `GIT~1`) would be likewise weakened, or whether that is too\ndangerous to allow even in `skip-worktree` entries.\n\nNot necessarily decisions you would want to burden a first-time\ncontributor with.\n\nCiao,\nDscho\n\n>\n> Philip\n>\n> [1]\n> https://github.com/git-for-windows/git/issues/2803#issuecomment-687161483\n>\n"},{"id":"405136","messageId":"nycvar.QRO.7.76.6.2009072051470.56@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"441bd08b-ca7d-5977-a455-c4c2a4bd4bc9@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-07T18:55:48Z","receivedAt":"2020-09-07T18:56:58Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Kaartic,\n\nOn Mon, 7 Sep 2020, Kaartic Sivaraam wrote:\n\n> On 28-08-2020 12:26, Jeff King wrote:\n> > Are we interested in participating in the December 2020 round of\n> > Outreachy? The community application period is now open.\n> >\n> > I can look into lining up funding, but we'd also need:\n> >\n> >   - volunteers to act as mentors\n> >\n>\n> I'm willing to co-mentor a project for this term. I don't have any\n> particular preference of projects, though.\n>\n> > I would appreciate help to find project ideas though. Are there still\n> > scripts that are worth converting to C (excluding git-bisect.sh and\n> > git-submodule.sh that are still worked on)?\n>\n> I think Dscho's e-mail linked below gives a nice overview of the various\n> scripts and their likely status as of Jan2020:\n>\n> https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n>\n> I'm guessing only the status of submodule has changed as it's being\n> worked on now.\n\nNo, not quite. The `git-merge-*.sh` ones I called \"trivial\" are already\nbeing worked on by Alban Gruin:\nhttps://lore.kernel.org/git/20200901105705.6059-1-alban.gruin@gmail.com/\n\nAnd `git-legacy-stash.sh` is no more, as of v2.27.0~180^2.\n\nBut yes, other than that, my summary still holds.\n\nCiao,\nDscho\n"},{"id":"405267","messageId":"20200909182617.GA14981@nand.local","threadId":"54148","inReplyTo":"20200903060041.GH4035286@google.com","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2020-09-09T18:26:17Z","receivedAt":"2020-09-09T18:26:29Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"Hi Jonathan,\n\nThanks for suggesting a great list of ideas. I don't have strong\nopinions on most of the above, so I'll save you a bunch of 'ack's and\njust talk about the ones that I do:\n\nOn Wed, Sep 02, 2020 at 11:00:41PM -0700, Jonathan Nieder wrote:\n> I think setting up something like snowpatch[*] to run CI on patches\n> that have hit the mailing list but not yet hit \"seen\" might be a good\n> project for an interested applicant (and I'd be interested in\n> co-mentoring if we find a taker).\n\nTo be honest, I'm not crazy about this one. We already have a system\nin place that works well (GitHub Actions) that allows people to run CI\non their patches automatically at no cost.\n\nI'm not saying that we shouldn't have another because of sticking to one\nprovider or another, but there has been a reasonable amount of churn\nthere, and what's in-tree now seems to be working quite well.\n\nThe goal of providing CI easily to new contributors should be to make it\nas *easy* as possible to test their patches, and adding an additional\ndecision (i.e., \"should I use GitHub Actions, or Snowpatch?\") seems\ncounter-intuitive.\n\n> - formats: on-disk reverse idx\n\nAs a heads up, I think that I am going to start working on (an\nalternative to) this myself, so it may be worth pushing future Outreachy\ninterns in a different direction.\n\n> Jonathan\n>\n> [*] https://github.com/ruscur/snowpatch\n\nThanks,\nTaylor\n"},{"id":"405300","messageId":"20200910021916.GA503@nand.local","threadId":"54148","inReplyTo":"20200910013915.GD667601@google.com","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2020-09-10T02:19:16Z","receivedAt":"2020-09-10T02:21:28Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Wed, Sep 09, 2020 at 06:39:15PM -0700, Jonathan Nieder wrote:\n> Taylor Blau wrote:\n> In other words: this isn't about changing how tests are executed ---\n> it's about going from patches on list to git commits that can be\n> tested.\n\nFair enough; it sounds like a Snowpatch-like tool might be useful for\nthat case.\n\n> [...]\n> >> - formats: on-disk reverse idx\n> >\n> > As a heads up, I think that I am going to start working on (an\n> > alternative to) this myself,\n>\n> Neat!  I look forward to seeing what you build.  (Is this related to\n> the bitmaps-using-midx-ordering work?)\n\nYou guessed it ;-). It's sort of a tricky issue: the pack-objects code\nneeds to know things like the position of an object in index order so\nthat it can look at the offset of the next object and determine its\nsize.\n\nBut, in the multi-pack case, things aren't so simple. It would be nice\nif we could look at a bit position and say \"you are at bit position N\nand there are M different packs before you, so I know what position\nyou are within your pack\", but this can't be done in general when you\nhave duplicate objects among packs in your MIDX.\n\nThe MIDX is only going to choose one of them, and so you don't know how\nmany \"holes\" are present before you. In my development version, I have a\nbitmap extension I'm calling the \"rev-cache\" which acts like a mapping\nbetween bit position and MIDX name order (which can then be used to look\nup auxiliary info like which pack an object came from, its position in\nthe pack's index order, and so on).\n\nBut, having an on-disk mapping between objects and their position in\ndifferent orderings will be useful not only for this, but for:\n\n  - avoiding building a reverse index in memory from scratch (which can\n    occupy quite a bit of the heap in some repositories that we see),\n    and\n\n  - dropping GitHub's custom \"bit-cache\" extension, which maps objects\n    from name order to bit position.\n\nAnyway, obviously not related to Outreachy, and obviously many more\ndetails to come once I have patches that are more mature, but I couldn't\nhelp myself in the meantime.\n\n> Thanks,\n> Jonathan\n>\n> >> [*] https://github.com/ruscur/snowpatch\n\nThanks,\nTaylor\n"},{"id":"405305","messageId":"20200910013915.GD667601@google.com","threadId":"54148","inReplyTo":"20200909182617.GA14981@nand.local","subject":"Re: Git in Outreachy?","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2020-09-10T01:39:15Z","receivedAt":"2020-09-10T02:48:07Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Taylor Blau wrote:\n> On Wed, Sep 02, 2020 at 11:00:41PM -0700, Jonathan Nieder wrote:\n\n>> I think setting up something like snowpatch[*] to run CI on patches\n>> that have hit the mailing list but not yet hit \"seen\" might be a good\n>> project for an interested applicant (and I'd be interested in\n>> co-mentoring if we find a taker).\n>\n> To be honest, I'm not crazy about this one. We already have a system\n> in place that works well (GitHub Actions) that allows people to run CI\n> on their patches automatically at no cost.\n\nI agree, that's good for people using GitGitGadget.  So if we're\nfocusing on individual contributors to Git, that may be enough (or\nhaving the ability to run tests on their own machine may be even\nbetter ;-)).\n\nBut a reviewer or maintainer cannot count on all contributors using\nGitGitGadget.  Hence a bridge from patches sent on the mailing list to\ngit commits that a system like GitHub Actions can consume becomes\nimportant.  Snowpatch is such a bridge.\n\nIn other words: this isn't about changing how tests are executed ---\nit's about going from patches on list to git commits that can be\ntested.\n\n[...]\n>> - formats: on-disk reverse idx\n>\n> As a heads up, I think that I am going to start working on (an\n> alternative to) this myself,\n\nNeat!  I look forward to seeing what you build.  (Is this related to\nthe bitmaps-using-midx-ordering work?)\n\nThanks,\nJonathan\n\n>> [*] https://github.com/ruscur/snowpatch\n"},{"id":"405558","messageId":"12c349f3-aeee-7e44-08fd-ae03b3f16dab@gmail.com","threadId":"54148","inReplyTo":"20200915173529.GA2859918@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2020-09-15T17:55:08Z","receivedAt":"2020-09-15T17:56:01Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 15-09-2020 23:05, Jeff King wrote:\n> On Thu, Sep 03, 2020 at 01:41:26AM -0400, Jeff King wrote:\n> \n>> I'm still working out funding details, but in the meantime we're signed\n>> up. Potential mentors should propose projects here:\n>>\n>>   https://www.outreachy.org/communities/cfp/git/\n>>\n>> Sooner is better than later. We can technically submit projects up until\n>> the 24th, but student applications are open now, and have to be in by\n>> September 20th.\n> \n> [Adding everybody to the cc list who has been in the Outreachy\n> thread this year...]\n> \n> AFAICT we still have no proposed projects nor signed-up mentors.\n\nJust to ensure I didn't miss anything, a person who's signing up as a\nmentor for an organization needs to propose a project or wait for one to\nbe proposed, right? Or is there some other way to express interest in\nmentoring without proposing a project?\n\nI ask this because I would be willing to sign up as a co-mentor for a\nproject in the organization but don't have any project proposals in\nmind. I only see a way to \"submit a project proposal\" in the following\npage:\n\n    https://www.outreachy.org/communities/cfp/git/\n\n> If you're interested in mentoring, the time to propose is definitely\n> ASAP.\n> \n-- \nSivaraam\n"},{"id":"405559","messageId":"20200915180219.GA2861525@coredump.intra.peff.net","threadId":"54148","inReplyTo":"12c349f3-aeee-7e44-08fd-ae03b3f16dab@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-09-15T18:02:19Z","receivedAt":"2020-09-15T18:08:27Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Sep 15, 2020 at 11:25:08PM +0530, Kaartic Sivaraam wrote:\n\n> >> I'm still working out funding details, but in the meantime we're signed\n> >> up. Potential mentors should propose projects here:\n> >>\n> >>   https://www.outreachy.org/communities/cfp/git/\n> >>\n> >> Sooner is better than later. We can technically submit projects up until\n> >> the 24th, but student applications are open now, and have to be in by\n> >> September 20th.\n> > \n> > [Adding everybody to the cc list who has been in the Outreachy\n> > thread this year...]\n> > \n> > AFAICT we still have no proposed projects nor signed-up mentors.\n> \n> Just to ensure I didn't miss anything, a person who's signing up as a\n> mentor for an organization needs to propose a project or wait for one to\n> be proposed, right? Or is there some other way to express interest in\n> mentoring without proposing a project?\n\nRight, mentors propose the projects they're willing to mentor.\n\n> I ask this because I would be willing to sign up as a co-mentor for a\n> project in the organization but don't have any project proposals in\n> mind. I only see a way to \"submit a project proposal\" in the following\n> page:\n> \n>     https://www.outreachy.org/communities/cfp/git/\n\nYeah, you'd have to either find the person you want to co-mentor with\nand work on a proposal with them, or wait for somebody to propose\nsomething and then ask if you could join them as a co-mentor.\n\n-Peff\n"},{"id":"405560","messageId":"20200915173529.GA2859918@coredump.intra.peff.net","threadId":"54148","inReplyTo":"20200903054126.GA2053272@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-09-15T17:35:29Z","receivedAt":"2020-09-15T18:44:24Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Sep 03, 2020 at 01:41:26AM -0400, Jeff King wrote:\n\n> I'm still working out funding details, but in the meantime we're signed\n> up. Potential mentors should propose projects here:\n> \n>   https://www.outreachy.org/communities/cfp/git/\n> \n> Sooner is better than later. We can technically submit projects up until\n> the 24th, but student applications are open now, and have to be in by\n> September 20th.\n\n[Adding everybody to the cc list who has been in the Outreachy\nthread this year...]\n\nAFAICT we still have no proposed projects nor signed-up mentors.\nInterns are actively applying _now_, so we are likely missing out on (or\nhave already missed out on) applicants.\n\nIf you're interested in mentoring, the time to propose is definitely\nASAP.\n\n-Peff\n"},{"id":"405604","messageId":"CAP8UFD3QD_DP7h_Pkv246O9_PehZKx9iW5PyFmT6HMYqJ=i2NQ@mail.gmail.com","threadId":"54148","inReplyTo":"CAP8UFD2rpNhDhyHdQNxS-KJZgcumsCpK_JQ5koCqXJd70s-+_w@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-16T06:42:40Z","receivedAt":"2020-09-16T06:42:58Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Aug 31, 2020 at 8:55 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> On Fri, Aug 28, 2020 at 8:56 AM Jeff King <peff@peff.net> wrote:\n\n> >   - updates to our applicant materials (proposed projects, but also\n> >     microproject / patch suggestions)\n>\n> It looks like many micro-project ideas from GSoC 2020 are still valid,\n> and I have a few new ones, so I am ok to create a micro-project page.\n\nHere is a new page with micro-project ideas for Outreachy applicants:\n\nhttps://git.github.io/Outreachy-21-Microprojects/\n\nI added only one new idea about modernizing test scripts, though I\nknow someone is already working on modernizing t7001. But I think it\ncan be applied to other test scripts.\n\nWhile at it I also removed the GSoC 2020 material from the home page\nand made a few cosmetic changes related to historical materials.\n"},{"id":"405607","messageId":"CAP8UFD0FGs8UNwu9i7aZt4wfr7=bOgZSVtJ9XAbSkMCY8V8fEQ@mail.gmail.com","threadId":"54148","inReplyTo":"20200901125119.GA3250129@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-16T08:45:07Z","receivedAt":"2020-09-16T08:45:27Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Sep 1, 2020 at 2:51 PM Jeff King <peff@peff.net> wrote:\n>\n> On Mon, Aug 31, 2020 at 11:05:37AM -0700, Emily Shaffer wrote:\n>\n> > I'm interested in mentoring or co-mentoring this term. (I'm not working\n> > this week but I didn't want to miss a deadline to volunteer.)\n>\n> OK, between you and Christian, then, it sounds like it's worth pursuing.\n> I'll sign us up and try to arrange funding.\n\nThanks for signing up and for having arranged some funding already! I\nmight get further funding from GitLab too.\n\n> > One thought I had was whether it might be cool to shop for another\n> > co-mentor from Wireshark and have an intern teach Wireshark how to\n> > decipher Git protocol. But it seems large, and maybe last-minute for\n> > this term.\n>\n> That sounds neat. I don't think it would be too large (in fact, I think\n> it might end up being a bit small for a whole-term project). It would\n> definitely require somebody from Wireshark being a co-mentor, though.\n\nI agree that it doesn't look too large. If it appears to be too large,\nit could be finished later either by the Outreachy intern who started\nit or by someone else like a GSoC student. Also it looks like all the\nprojects will be last minute anyway.\n"},{"id":"405608","messageId":"CAP8UFD31B9YgninC2Fyb=0+OVY7E4SW7LGBbx9E7CrgSn+95BA@mail.gmail.com","threadId":"54148","inReplyTo":"nycvar.QRO.7.76.6.2009020558550.56@tvgsbejvaqbjf.bet","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-16T09:01:52Z","receivedAt":"2020-09-16T09:02:15Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Dscho,\n\nOn Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n\n> As to projects, I would like to believe that\n> https://github.com/gitgitgadget/git/issues has grown into a useful\n> resource.\n\nThanks for the useful resource!\n\nI would be interested in mentoring, or better co-mentoring, the\nfollowing projects:\n\n- Accelerate rename detection and range-diff\n(https://github.com/gitgitgadget/git/issues/519): ideally I would\nco-mentor with someone a bit familiar with the suggested algorithms.\n- Add support for drop!/reword! commits to `git rebase -i`\n(https://github.com/gitgitgadget/git/issues/259,\nhttps://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n- Invent a way to retain reflogs for a while after the ref was deleted\n(https://github.com/gitgitgadget/git/issues/236): I guess this might\nbe implemented as part of the new `git maintenance` builtin.\n\nBest,\nChristian.\n"},{"id":"405609","messageId":"CAP8UFD22MJ4YygF_XgYykHAPjp66jbndgyT3g2F9AL0PiiWdSQ@mail.gmail.com","threadId":"54148","inReplyTo":"20200903060041.GH4035286@google.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-16T09:12:13Z","receivedAt":"2020-09-16T09:12:34Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Thu, Sep 3, 2020 at 8:00 AM Jonathan Nieder <jrnieder@gmail.com> wrote:\n\n> Christian Couder wrote:\n>\n> > I would appreciate help to find project ideas though. Are there still\n> > scripts that are worth converting to C (excluding git-bisect.sh and\n> > git-submodule.sh that are still worked on)? Are there worthy\n> > refactorings or improvements that we could propose as projects?\n>\n> I think setting up something like snowpatch[*] to run CI on patches\n> that have hit the mailing list but not yet hit \"seen\" might be a good\n> project for an interested applicant (and I'd be interested in\n> co-mentoring if we find a taker).\n\nI'd prefer not co-mentoring this one. If this is the only one you'd be\nok to co-mentor I could reconsider though.\n\n> Some other topics that could be interesting:\n> - better support for handling people's name changing\n\nFollowing discussions about mailmap, name changes, deadnames, etc\nduring the Inclusion Summit yesterday and the day before, I am\ninterested in co-mentoring such a project along what has been\ndiscussed.\n\n> - making signing features such as signed push easier to use (for\n>   example by allowing signing with SSH keys to simplify PKI) and more\n>   useful (for example by standardizing a way to publish signed push\n>   logs in Git)\n> - protocol: sharing notes and branch descriptions\n> - formats: on-disk reverse idx\n> - obliterate\n> - cache server to take advantage of multiple promisors+packfile URIs\n\nWould you be ok to elaborate about the above projects? I am not very\nmuch excited about any of them, but I would be ok to co-mentor as long\nas my co-mentor would come up with a proper project description.\n\nThanks,\nChristian.\n"},{"id":"405610","messageId":"CAP8UFD0_75zR3xoBzbVZjgTY2+KvORLFNMZ36s8+m6KZyNTXPg@mail.gmail.com","threadId":"54148","inReplyTo":"nycvar.QRO.7.76.6.2009072051470.56@tvgsbejvaqbjf.bet","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-16T09:35:36Z","receivedAt":"2020-09-16T09:35:55Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Dscho and Kaartic,\n\nOn Mon, Sep 7, 2020 at 8:55 PM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n\n> On Mon, 7 Sep 2020, Kaartic Sivaraam wrote:\n>\n> > On 28-08-2020 12:26, Jeff King wrote:\n> > > Are we interested in participating in the December 2020 round of\n> > > Outreachy? The community application period is now open.\n> > >\n> > > I can look into lining up funding, but we'd also need:\n> > >\n> > >   - volunteers to act as mentors\n> > >\n> >\n> > I'm willing to co-mentor a project for this term. I don't have any\n> > particular preference of projects, though.\n\nThanks!\n\n> > > I would appreciate help to find project ideas though. Are there still\n> > > scripts that are worth converting to C (excluding git-bisect.sh and\n> > > git-submodule.sh that are still worked on)?\n> >\n> > I think Dscho's e-mail linked below gives a nice overview of the various\n> > scripts and their likely status as of Jan2020:\n> >\n> > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n> >\n> > I'm guessing only the status of submodule has changed as it's being\n> > worked on now.\n>\n> No, not quite. The `git-merge-*.sh` ones I called \"trivial\" are already\n> being worked on by Alban Gruin:\n> https://lore.kernel.org/git/20200901105705.6059-1-alban.gruin@gmail.com/\n>\n> And `git-legacy-stash.sh` is no more, as of v2.27.0~180^2.\n>\n> But yes, other than that, my summary still holds.\n\nTo summarize more, it seems to me that only the following scripts\ncould be worth converting:\n\ngit-difftool--helper.sh\ngit-mergetool--lib.sh\ngit-mergetool.sh\n\nI wonder if they are really worth converting though, as they should\nprobably all be converted together and we would likely also need to\nconvert the scripts in mergetools/ at the same time. And then there\nshould be a way to still easily configure things for users. So perhaps\na better way to approach this would be first to convert the scripts in\nmergetools/ into config files.\n\nBest,\nChristian.\n"},{"id":"405611","messageId":"0244caba-8075-e742-9c05-55c320aef64e@gmail.com","threadId":"54148","inReplyTo":"CAP8UFD31B9YgninC2Fyb=0+OVY7E4SW7LGBbx9E7CrgSn+95BA@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2020-09-16T09:45:46Z","receivedAt":"2020-09-16T09:45:56Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"On 16/09/2020 10:01, Christian Couder wrote:\n> Hi Dscho,\n> \n> On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n> \n>> As to projects, I would like to believe that\n>> https://github.com/gitgitgadget/git/issues has grown into a useful\n>> resource.\n> \n> Thanks for the useful resource!\n> \n> I would be interested in mentoring, or better co-mentoring, the\n> following projects:\n> \n> - Accelerate rename detection and range-diff\n> (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> co-mentor with someone a bit familiar with the suggested algorithms.\n> - Add support for drop!/reword! commits to `git rebase -i`\n> (https://github.com/gitgitgadget/git/issues/259,\n> https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n\nI've got some patches that implement the reword! part (or something very \nsimilar) at [1]. I've never ended up using them that much so haven't \npushed them forward.\n\nBest Wishes\n\nPhillip\n\n[1] https://github.com/phillipwood/git/commits/wip/rebase-amend\n\n> - Invent a way to retain reflogs for a while after the ref was deleted\n> (https://github.com/gitgitgadget/git/issues/236): I guess this might\n> be implemented as part of the new `git maintenance` builtin.\n> \n> Best,\n> Christian.\n> \n"},{"id":"405651","messageId":"nycvar.QRO.7.76.6.2009162040420.56@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"5be2fca8-2dbd-115e-b3bb-5783daeba4a3@iee.email","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-16T18:43:17Z","receivedAt":"2020-09-16T18:43:52Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Philip,\n\nOn Wed, 16 Sep 2020, Philip Oakley wrote:\n\n> On 07/09/2020 19:49, Johannes Schindelin wrote:\n> >\n> > On Fri, 4 Sep 2020, Philip Oakley wrote:\n> >\n> >> On 03/09/2020 07:00, Jonathan Nieder wrote:\n> >>> Christian Couder wrote:\n> >>>\n> >>>> I would appreciate help to find project ideas though. Are there still\n> >>>> scripts that are worth converting to C (excluding git-bisect.sh and\n> >>>> git-submodule.sh that are still worked on)? Are there worthy\n> >>>> refactorings or improvements that we could propose as projects?\n> >>> I think setting up something like snowpatch[*] to run CI on patches\n> >>> that have hit the mailing list but not yet hit \"seen\" might be a good\n> >>> project for an interested applicant (and I'd be interested in\n> >>> co-mentoring if we find a taker).\n> >>>\n> >>> Some other topics that could be interesting:\n> >>> - better support for handling people's name changing\n> >>> - making signing features such as signed push easier to use (for\n> >>>   example by allowing signing with SSH keys to simplify PKI) and more\n> >>>   useful (for example by standardizing a way to publish signed push\n> >>>   logs in Git)\n> >>> - protocol: sharing notes and branch descriptions\n> >>> - formats: on-disk reverse idx\n> >>> - obliterate\n> >>> - cache server to take advantage of multiple promisors+packfile URIs\n> >>>\n> >>> Jonathan\n> >>>\n> >>> [*] https://github.com/ruscur/snowpatch\n> >> A suggestion with high value for the Windows community\n> >> - mechanism to map file names between the index and the local FS, should\n> >> a repos file/path name already be taken, or invalid. [1]\n> > This suggestion keeps coming up, but I cannot help but highly doubt that\n> > it will prove useful in practice: if your source code contains a file\n> > called `aux.c`, chances are that your build system lists this file\n> > specifically, and it won't do at all to \"magically\" rename it to, say,\n> > `aux_.c` during checkout.\n>\n> I'd disagree with that line of reasoning in the sense that if someone is\n> on Windows wanting to 'view' a repo that was developed on Linux, with\n> colons in pathnames, and filenames like aux.c we shouldn't be\n> deliberately de-include them just because of those file/pathname\n> 'accidents.\n\nIf someone wanted to just have a look, they usually make use of the web\ninterface of a Git hosting service and look at the file there.\n\nEven if somebody insists on cloning the entire history, they can easily\nlook at the file via `git show origin/HEAD:<path>`.\n\nThe most likely users who really need those files to be checked out are\nthe ones who need to build the project, and that's simply not possible\nwith \"magically\" renamed files.\n\nCiao,\nDscho\n"},{"id":"405681","messageId":"nycvar.QRO.7.76.6.2009162206580.56@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"CAP8UFD0_75zR3xoBzbVZjgTY2+KvORLFNMZ36s8+m6KZyNTXPg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-16T20:27:40Z","receivedAt":"2020-09-16T20:28:09Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Christian,\n\nOn Wed, 16 Sep 2020, Christian Couder wrote:\n\n> On Mon, Sep 7, 2020 at 8:55 PM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n>\n> > On Mon, 7 Sep 2020, Kaartic Sivaraam wrote:\n> >\n> > > On 28-08-2020 12:26, Jeff King wrote:\n> > >\n> > > > I would appreciate help to find project ideas though. Are there\n> > > > still scripts that are worth converting to C (excluding\n> > > > git-bisect.sh and git-submodule.sh that are still worked on)?\n> > >\n> > > I think Dscho's e-mail linked below gives a nice overview of the\n> > > various scripts and their likely status as of Jan2020:\n> > >\n> > > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n> > >\n> > > I'm guessing only the status of submodule has changed as it's being\n> > > worked on now.\n> >\n> > No, not quite. The `git-merge-*.sh` ones I called \"trivial\" are already\n> > being worked on by Alban Gruin:\n> > https://lore.kernel.org/git/20200901105705.6059-1-alban.gruin@gmail.com/\n> >\n> > And `git-legacy-stash.sh` is no more, as of v2.27.0~180^2.\n> >\n> > But yes, other than that, my summary still holds.\n>\n> To summarize more, it seems to me that only the following scripts\n> could be worth converting:\n>\n> git-difftool--helper.sh\n> git-mergetool--lib.sh\n> git-mergetool.sh\n>\n> I wonder if they are really worth converting though, as they should\n> probably all be converted together and we would likely also need to\n> convert the scripts in mergetools/ at the same time. And then there\n> should be a way to still easily configure things for users. So perhaps\n> a better way to approach this would be first to convert the scripts in\n> mergetools/ into config files.\n\nThe biggest problem is that they're all entangled.\n`git-difftool--helper.sh` sources `git-mergetool--lib.sh` and uses quite a\nbit of its machinery.\n\nAs to converting the scripts to config files, I'd rather have them\nhard-coded in the source code. Something along those lines:\n\nstruct mergetool {\n\tconst char *can_merge;\n\tconst char *can_diff;\n\tconst char *diff_cmd\n\tconst char *merge_cmd;\n\tconst char *translate_merge_tool_path;\n\tconst char *list_tool_variants;\n\tconst char *exit_code_trustable;\n} araxis = {\n\t.diff_cmd = \"\\\"$merge_tool_path\"\\ -wait -2 \\\"$LOCAL\\\" \\\"$REMOTE\\\" >/dev/null 2>&1\",\n\t.merge_cmd = \"if $base_present\\n\"\n\t\t\"then\\n\"\n\t\t\" \\\"$merge_tool_path\\\" -wait -merge -3 -a1\"\n\t\t\"  \\\"$BASE\\\" \\\"$LOCAL\\\" \\\"$REMOTE\\\" \\\"$MERGED\\\" >/dev/null 2>&1\\n\"\n\t\t\"else\\n\"\n                \" \\\"$merge_tool_path\\\" -wait -2\"\n\t\t\"  \\\"$LOCAL\\\" \\\"$REMOTE\\\" \\\"$MERGED\\\" >/dev/null 2>&1\\n\"\n\t\t\"fi\",\n\t.translate_merge_tool_path = \"echo compare\"\n}, [...]\n\nI would then probably try to implement the bare minimum for the\n`difftool--helper` command to work (re-implementing in C only the parts of\n`mergetool--lib` that are necessary), and only in a next patch series work\non `mergetool`.\n\nCiao,\nDscho\n"},{"id":"405690","messageId":"5be2fca8-2dbd-115e-b3bb-5783daeba4a3@iee.email","threadId":"54148","inReplyTo":"nycvar.QRO.7.76.6.2009060933480.56@tvgsbejvaqbjf.bet","subject":"Re: Git in Outreachy?","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-09-16T15:16:37Z","receivedAt":"2020-09-16T20:56:49Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Hi, Sorry I've not been able to attend to the list discussions recently.\n\nOn 07/09/2020 19:49, Johannes Schindelin wrote:\n> Hi Philip,\n>\n> On Fri, 4 Sep 2020, Philip Oakley wrote:\n>\n>> On 03/09/2020 07:00, Jonathan Nieder wrote:\n>>> Christian Couder wrote:\n>>>\n>>>> I would appreciate help to find project ideas though. Are there still\n>>>> scripts that are worth converting to C (excluding git-bisect.sh and\n>>>> git-submodule.sh that are still worked on)? Are there worthy\n>>>> refactorings or improvements that we could propose as projects?\n>>> I think setting up something like snowpatch[*] to run CI on patches\n>>> that have hit the mailing list but not yet hit \"seen\" might be a good\n>>> project for an interested applicant (and I'd be interested in\n>>> co-mentoring if we find a taker).\n>>>\n>>> Some other topics that could be interesting:\n>>> - better support for handling people's name changing\n>>> - making signing features such as signed push easier to use (for\n>>>   example by allowing signing with SSH keys to simplify PKI) and more\n>>>   useful (for example by standardizing a way to publish signed push\n>>>   logs in Git)\n>>> - protocol: sharing notes and branch descriptions\n>>> - formats: on-disk reverse idx\n>>> - obliterate\n>>> - cache server to take advantage of multiple promisors+packfile URIs\n>>>\n>>> Jonathan\n>>>\n>>> [*] https://github.com/ruscur/snowpatch\n>> A suggestion with high value for the Windows community\n>> - mechanism to map file names between the index and the local FS, should\n>> a repos file/path name already be taken, or invalid. [1]\n> This suggestion keeps coming up, but I cannot help but highly doubt that\n> it will prove useful in practice: if your source code contains a file\n> called `aux.c`, chances are that your build system lists this file\n> specifically, and it won't do at all to \"magically\" rename it to, say,\n> `aux_.c` during checkout.\n\nI'd disagree with that line of reasoning in the sense that if someone is\non Windows wanting to 'view' a repo that was developed on Linux, with\ncolons in pathnames, and filenames like aux.c we shouldn't be\ndeliberately de-include them just because of those file/pathname\n'accidents. I accept that the build system probably won't be working for\ntheir Windows environment (how could it be?), but, if possible, we\nshould be able to support them, in some positive way. In our distributed\ncollaborative environment we can trip over the user's  'your file / your\nbuild' tag.\n\n> In contrast, I think a much more useful project would be to relax the\n> `core.protectNTFS` protections to cover only the files that will be\n> written to disk, and not bother even checking the files excluded from a\n> sparse-checkout for invalid file names on NTFS.\n\nThat's a valid base method for all the NTFS valid file and path names.\n\nThe next level could be a mechanism for path and file name adjustment,\nat least for a _copy-out_ step (without ability to 'git add' / check\nback in).\n>\n> This is trickier, of course, than meets the eye: we would still want to be\n> _very_ careful to ensure that the unchecked file names will _never_ make\n> it to the disk. And, slightly related, the question whether checking for\n> `.git` (or `GIT~1`) would be likewise weakened, or whether that is too\n> dangerous to allow even in `skip-worktree` entries.\n\nAgree that the security aspects of `.Git` etc must still be retained.\n>\n> Not necessarily decisions you would want to burden a first-time\n> contributor with.\n\nTrue, but still worth recording as a useful Git project (and that there\nare a number of nuances within it!)\n\n--\nPhilip\n\n> Ciao,\n> Dscho\n>\n>> Philip\n>>\n>> [1]\n>> https://github.com/git-for-windows/git/issues/2803#issuecomment-687161483\n>>\n\n"},{"id":"405734","messageId":"CAP8UFD1n_PYzygFCgNDt3T=EQhbcuaTYFCfNN5n45OHRh45KOg@mail.gmail.com","threadId":"54148","inReplyTo":"CAP8UFD31B9YgninC2Fyb=0+OVY7E4SW7LGBbx9E7CrgSn+95BA@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-17T09:43:52Z","receivedAt":"2020-09-17T09:44:13Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Wed, Sep 16, 2020 at 11:01 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n\n> On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n>\n> > As to projects, I would like to believe that\n> > https://github.com/gitgitgadget/git/issues has grown into a useful\n> > resource.\n>\n> Thanks for the useful resource!\n>\n> I would be interested in mentoring, or better co-mentoring, the\n> following projects:\n>\n> - Accelerate rename detection and range-diff\n> (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> co-mentor with someone a bit familiar with the suggested algorithms.\n\nProposed on Outreachy's website:\n\nhttps://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/\n\n> - Add support for drop!/reword! commits to `git rebase -i`\n> (https://github.com/gitgitgadget/git/issues/259,\n> https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n> - Invent a way to retain reflogs for a while after the ref was deleted\n> (https://github.com/gitgitgadget/git/issues/236): I guess this might\n> be implemented as part of the new `git maintenance` builtin.\n\nI will also likely submit a proposal for one of the above projects.\n"},{"id":"405736","messageId":"ed35b0ac-a2c6-c25d-db39-284e7daf29e8@gmail.com","threadId":"54148","inReplyTo":"CAP8UFD1n_PYzygFCgNDt3T=EQhbcuaTYFCfNN5n45OHRh45KOg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2020-09-17T10:14:36Z","receivedAt":"2020-09-17T10:14:44Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"On 17/09/2020 10:43, Christian Couder wrote:\n> On Wed, Sep 16, 2020 at 11:01 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n> \n>> On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n>> <Johannes.Schindelin@gmx.de> wrote:\n>>\n>>> As to projects, I would like to believe that\n>>> https://github.com/gitgitgadget/git/issues has grown into a useful\n>>> resource.\n>>\n>> Thanks for the useful resource!\n>>\n>> I would be interested in mentoring, or better co-mentoring, the\n>> following projects:\n>>\n>> - Accelerate rename detection and range-diff\n>> (https://github.com/gitgitgadget/git/issues/519): ideally I would\n>> co-mentor with someone a bit familiar with the suggested algorithms.\n> \n> Proposed on Outreachy's website:\n> \n> https://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/\n> \n>> - Add support for drop!/reword! commits to `git rebase -i`\n>> (https://github.com/gitgitgadget/git/issues/259,\n>> https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n\nI'd be happy to support someone working on this though not necessarily \nas a formal co-mentor - what the time (and other) commitments does being \na co-mentor involve?\n\nBest Wishes\n\nPhillip\n\n>> - Invent a way to retain reflogs for a while after the ref was deleted\n>> (https://github.com/gitgitgadget/git/issues/236): I guess this might\n>> be implemented as part of the new `git maintenance` builtin.\n> \n> I will also likely submit a proposal for one of the above projects.\n> \n"},{"id":"405762","messageId":"0ef7ad0b-4626-2cca-d29c-35d21412e595@iee.email","threadId":"54148","inReplyTo":"nycvar.QRO.7.76.6.2009162040420.56@tvgsbejvaqbjf.bet","subject":"Re: Git in Outreachy?","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-09-17T14:42:47Z","receivedAt":"2020-09-17T15:35:32Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Hi Dscho,\n\nOn 16/09/2020 19:43, Johannes Schindelin wrote:\n> Hi Philip,\n>\n> On Wed, 16 Sep 2020, Philip Oakley wrote:\n>\n>> On 07/09/2020 19:49, Johannes Schindelin wrote:\n>>> On Fri, 4 Sep 2020, Philip Oakley wrote:\n>>>\n>>>> On 03/09/2020 07:00, Jonathan Nieder wrote:\n>>>>> Christian Couder wrote:\n>>>>>\n>>>>>> I would appreciate help to find project ideas though. Are there still\n>>>>>> scripts that are worth converting to C (excluding git-bisect.sh and\n>>>>>> git-submodule.sh that are still worked on)? Are there worthy\n>>>>>> refactorings or improvements that we could propose as projects?\n>>>>> I think setting up something like snowpatch[*] to run CI on patches\n>>>>> that have hit the mailing list but not yet hit \"seen\" might be a good\n>>>>> project for an interested applicant (and I'd be interested in\n>>>>> co-mentoring if we find a taker).\n>>>>>\n>>>>> Some other topics that could be interesting:\n>>>>> - better support for handling people's name changing\n>>>>> - making signing features such as signed push easier to use (for\n>>>>>   example by allowing signing with SSH keys to simplify PKI) and more\n>>>>>   useful (for example by standardizing a way to publish signed push\n>>>>>   logs in Git)\n>>>>> - protocol: sharing notes and branch descriptions\n>>>>> - formats: on-disk reverse idx\n>>>>> - obliterate\n>>>>> - cache server to take advantage of multiple promisors+packfile URIs\n>>>>>\n>>>>> Jonathan\n>>>>>\n>>>>> [*] https://github.com/ruscur/snowpatch\n>>>> A suggestion with high value for the Windows community\n>>>> - mechanism to map file names between the index and the local FS, should\n>>>> a repos file/path name already be taken, or invalid. [1]\n>>> This suggestion keeps coming up, but I cannot help but highly doubt that\n>>> it will prove useful in practice: if your source code contains a file\n>>> called `aux.c`, chances are that your build system lists this file\n>>> specifically, and it won't do at all to \"magically\" rename it to, say,\n>>> `aux_.c` during checkout.\n>> I'd disagree with that line of reasoning in the sense that if someone is\n>> on Windows wanting to 'view' a repo that was developed on Linux, with\n>> colons in pathnames, and filenames like aux.c we shouldn't be\n>> deliberately de-include them just because of those file/pathname\n>> 'accidents.\n> If someone wanted to just have a look, they usually make use of the web\n> interface of a Git hosting service and look at the file there.\n>\n> Even if somebody insists on cloning the entire history, they can easily\n> look at the file via `git show origin/HEAD:<path>`.\n>\n> The most likely users who really need those files to be checked out are\n> the ones who need to build the project, and that's simply not possible\n> with \"magically\" renamed files.\n>\n> Ciao,\n> Dscho\nIs that the user experience we want to have?\n\nMaybe we need extra documentation on the core.protectNTFS setting noting\nthat Git itself may not be the right tool for such repositories, and\nthese workarounds which may not be familiar to many users.\n\nIt feels as if we are giving cart-blanche to bad actors who can add an\naux.info or similar files to a repo just to thwart collaborators being\non Windows.\n\nPhilip\n\n\n"},{"id":"405765","messageId":"CABPp-BHV5-UUio69b1ZnwuRwyj66HUEy3A24wvxELorR_1FB=g@mail.gmail.com","threadId":"54148","inReplyTo":"CAP8UFD1n_PYzygFCgNDt3T=EQhbcuaTYFCfNN5n45OHRh45KOg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2020-09-17T15:34:58Z","receivedAt":"2020-09-17T15:43:27Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Thu, Sep 17, 2020 at 2:47 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> On Wed, Sep 16, 2020 at 11:01 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n>\n> > On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n> > <Johannes.Schindelin@gmx.de> wrote:\n> >\n> > > As to projects, I would like to believe that\n> > > https://github.com/gitgitgadget/git/issues has grown into a useful\n> > > resource.\n> >\n> > Thanks for the useful resource!\n> >\n> > I would be interested in mentoring, or better co-mentoring, the\n> > following projects:\n> >\n> > - Accelerate rename detection and range-diff\n> > (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> > co-mentor with someone a bit familiar with the suggested algorithms.\n>\n> Proposed on Outreachy's website:\n>\n> https://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/\n\nAs a heads up, I'm going to be sending many patches modifying quite a\nwide range of diffcore-rename.c in the coming months for accelerating\nrename detection.  Maybe I'll get them all upstreamed before outreachy\nstarts, but that's not so clear.  As I mentioned in the gitgitgadget\nissue, the ideas outlined there and the methods I implemented are\ndifferent and complementary, but there is a pretty large risk of\nconflicts we need to resolve if I don't finish landing all my patches\nfirst.\n\n>\n> > - Add support for drop!/reword! commits to `git rebase -i`\n> > (https://github.com/gitgitgadget/git/issues/259,\n> > https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n> > - Invent a way to retain reflogs for a while after the ref was deleted\n> > (https://github.com/gitgitgadget/git/issues/236): I guess this might\n> > be implemented as part of the new `git maintenance` builtin.\n>\n> I will also likely submit a proposal for one of the above projects.\n"},{"id":"405841","messageId":"CAP8UFD0dsNbfR_uvWv7TmMBDXiO9paGpTex2HvGEofwSgL+GuQ@mail.gmail.com","threadId":"54148","inReplyTo":"ed35b0ac-a2c6-c25d-db39-284e7daf29e8@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-18T08:37:05Z","receivedAt":"2020-09-18T08:37:23Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Sep 17, 2020 at 12:14 PM Phillip Wood <phillip.wood123@gmail.com> wrote:\n>\n> On 17/09/2020 10:43, Christian Couder wrote:\n> > On Wed, Sep 16, 2020 at 11:01 AM Christian Couder\n> > <christian.couder@gmail.com> wrote:\n> >\n> >> On Wed, Sep 2, 2020 at 10:50 AM Johannes Schindelin\n> >> <Johannes.Schindelin@gmx.de> wrote:\n> >>\n> >>> As to projects, I would like to believe that\n> >>> https://github.com/gitgitgadget/git/issues has grown into a useful\n> >>> resource.\n> >>\n> >> Thanks for the useful resource!\n> >>\n> >> I would be interested in mentoring, or better co-mentoring, the\n> >> following projects:\n> >>\n> >> - Accelerate rename detection and range-diff\n> >> (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> >> co-mentor with someone a bit familiar with the suggested algorithms.\n> >\n> > Proposed on Outreachy's website:\n> >\n> > https://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/\n> >\n> >> - Add support for drop!/reword! commits to `git rebase -i`\n> >> (https://github.com/gitgitgadget/git/issues/259,\n> >> https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n>\n> I'd be happy to support someone working on this though not necessarily\n> as a formal co-mentor\n\nOk, I have submitted it then:\n\nhttps://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/improve-droping-and-rewording-commits-in-git-inter/cfp/\n\n> - what the time (and other) commitments does being\n> a co-mentor involve?\n\nThe above page should have a link/button to let you apply as a\nco-mentor and when you do that it should explain the requirements in\ndetail. I think though that the time you will actually spend on\nmentoring depends a lot on the intern that will be selected and on how\nmuch time you and I will be willing to spend.\n\nThanks!\n"},{"id":"405842","messageId":"CAP8UFD1BmhT29r5TtZJt5DMTsrPaJ11wNb-Hm-N7yTrppgn3Vg@mail.gmail.com","threadId":"54148","inReplyTo":"CABPp-BHV5-UUio69b1ZnwuRwyj66HUEy3A24wvxELorR_1FB=g@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-18T08:42:37Z","receivedAt":"2020-09-18T08:42:52Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Sep 17, 2020 at 5:35 PM Elijah Newren <newren@gmail.com> wrote:\n>\n> On Thu, Sep 17, 2020 at 2:47 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n\n> > Proposed on Outreachy's website:\n> >\n> > https://www.outreachy.org/outreachy-december-2020-internship-round/communities/git/accelerate-rename-detection-and-the-range-diff-com/cfp/\n>\n> As a heads up, I'm going to be sending many patches modifying quite a\n> wide range of diffcore-rename.c in the coming months for accelerating\n> rename detection.  Maybe I'll get them all upstreamed before outreachy\n> starts, but that's not so clear.\n\nIt starts at the beginning of December, so I think there is still time\nfor you to get them upstreamed.\n\n> As I mentioned in the gitgitgadget\n> issue, the ideas outlined there and the methods I implemented are\n> different and complementary, but there is a pretty large risk of\n> conflicts we need to resolve if I don't finish landing all my patches\n> first.\n\nIt could be a learning experience anyway for the intern, and in my\nexperience it has never been a big problem before, so I am not very\nworried about this.\n\nThanks for the heads up!\n> >\n> > > - Add support for drop!/reword! commits to `git rebase -i`\n> > > (https://github.com/gitgitgadget/git/issues/259,\n> > > https://public-inbox.org/git/alpine.DEB.2.21.1.1710151754070.40514@virtualbox/)\n> > > - Invent a way to retain reflogs for a while after the ref was deleted\n> > > (https://github.com/gitgitgadget/git/issues/236): I guess this might\n> > > be implemented as part of the new `git maintenance` builtin.\n> >\n> > I will also likely submit a proposal for one of the above projects.\n"},{"id":"405928","messageId":"CAP8UFD1BxnOk4-gaUQb9bY5zhAtD8Jy-x0RC=pNMSQvUaVxRmg@mail.gmail.com","threadId":"54148","inReplyTo":"nycvar.QRO.7.76.6.2009162206580.56@tvgsbejvaqbjf.bet","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-19T07:40:56Z","receivedAt":"2020-09-19T07:41:11Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Dscho,\n\nOn Wed, Sep 16, 2020 at 10:27 PM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n\n> On Wed, 16 Sep 2020, Christian Couder wrote:\n\n> > To summarize more, it seems to me that only the following scripts\n> > could be worth converting:\n> >\n> > git-difftool--helper.sh\n> > git-mergetool--lib.sh\n> > git-mergetool.sh\n> >\n> > I wonder if they are really worth converting though, as they should\n> > probably all be converted together and we would likely also need to\n> > convert the scripts in mergetools/ at the same time. And then there\n> > should be a way to still easily configure things for users. So perhaps\n> > a better way to approach this would be first to convert the scripts in\n> > mergetools/ into config files.\n>\n> The biggest problem is that they're all entangled.\n> `git-difftool--helper.sh` sources `git-mergetool--lib.sh` and uses quite a\n> bit of its machinery.\n\nYeah, I agree this is an issue.\n\n> As to converting the scripts to config files, I'd rather have them\n> hard-coded in the source code.\n\nI am not sure what are the pros and cons of hardcoding vs config files\nin this case.\n\nMy opinion is that config files would make it easier for people to\ncontribute what's needed for new tools, while hardcoding might make it\nmore easily extensible for us and might reduce backward compatibility\nissues.\n\n> I would then probably try to implement the bare minimum for the\n> `difftool--helper` command to work (re-implementing in C only the parts of\n> `mergetool--lib` that are necessary), and only in a next patch series work\n> on `mergetool`.\n\nThanks for your opinion on this. For now I think it needs to be\ndiscussed more before we could suggest it as a project.\n\nBest,\nChristian.\n"},{"id":"405929","messageId":"CAP8UFD3NxmBDDr4yqhOjmdUNVZYe6w4vW-TnqbkUO_zuFvKvpw@mail.gmail.com","threadId":"54148","inReplyTo":"20200915173529.GA2859918@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-19T08:12:38Z","receivedAt":"2020-09-19T08:12:53Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Sep 15, 2020 at 7:35 PM Jeff King <peff@peff.net> wrote:\n>\n> On Thu, Sep 03, 2020 at 01:41:26AM -0400, Jeff King wrote:\n>\n> > I'm still working out funding details, but in the meantime we're signed\n> > up. Potential mentors should propose projects here:\n> >\n> >   https://www.outreachy.org/communities/cfp/git/\n> >\n> > Sooner is better than later. We can technically submit projects up until\n> > the 24th, but student applications are open now, and have to be in by\n> > September 20th.\n>\n> [Adding everybody to the cc list who has been in the Outreachy\n> thread this year...]\n>\n> AFAICT we still have no proposed projects nor signed-up mentors.\n\nIt seems that we now have only the 2 projects I proposed and only 1\nsigned-up mentor (me).\n\nIt looks like Jonathan and Emily are reaching out to the Wireshark\ncommunity to find a co-mentor which is great! So we might have another\nproject and the associated mentors soon.\n\nOutreachy organizers have extended the mentor project submission\ndeadline though. The new deadline is Sept. 29, 2020 at 4pm UTC. They\nalso say that this deadline is a hard deadline, as the contribution\nperiod opens October 1, and they cannot add new projects after that\ndate.\n\n> Interns are actively applying _now_, so we are likely missing out on (or\n> have already missed out on) applicants.\n>\n> If you're interested in mentoring, the time to propose is definitely\n> ASAP.\n\nSure. By the way if you are interested in mentoring or co-mentoring,\nthen signing-up is not definitive, you can always decide not to mentor\nat all later for any reason as long as an intern has not been selected\nyet. (Intern selection deadline is Nov. 9, 2020.)\n"},{"id":"405937","messageId":"c1fb4d61-2a7a-8c8e-f2e3-d0b4ca75ff82@gmail.com","threadId":"54148","inReplyTo":"CAP8UFD3NxmBDDr4yqhOjmdUNVZYe6w4vW-TnqbkUO_zuFvKvpw@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2020-09-19T15:10:14Z","receivedAt":"2020-09-19T15:10:18Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"On 19/09/2020 09:12, Christian Couder wrote:\n> On Tue, Sep 15, 2020 at 7:35 PM Jeff King <peff@peff.net> wrote:\n>>\n>> On Thu, Sep 03, 2020 at 01:41:26AM -0400, Jeff King wrote:\n>>\n>>> I'm still working out funding details, but in the meantime we're signed\n>>> up. Potential mentors should propose projects here:\n>>>\n>>>    https://www.outreachy.org/communities/cfp/git/\n>>>\n>>> Sooner is better than later. We can technically submit projects up until\n>>> the 24th, but student applications are open now, and have to be in by\n>>> September 20th.\n>>\n>> [Adding everybody to the cc list who has been in the Outreachy\n>> thread this year...]\n>>\n>> AFAICT we still have no proposed projects nor signed-up mentors.\n> \n> It seems that we now have only the 2 projects I proposed and only 1\n> signed-up mentor (me).\n\nI've been accepted as a co-mentor on the rebase project now.\n\nBest Wishes\n\nPhillip\n\n> It looks like Jonathan and Emily are reaching out to the Wireshark\n> community to find a co-mentor which is great! So we might have another\n> project and the associated mentors soon.\n> \n> Outreachy organizers have extended the mentor project submission\n> deadline though. The new deadline is Sept. 29, 2020 at 4pm UTC. They\n> also say that this deadline is a hard deadline, as the contribution\n> period opens October 1, and they cannot add new projects after that\n> date.\n> \n>> Interns are actively applying _now_, so we are likely missing out on (or\n>> have already missed out on) applicants.\n>>\n>> If you're interested in mentoring, the time to propose is definitely\n>> ASAP.\n> \n> Sure. By the way if you are interested in mentoring or co-mentoring,\n> then signing-up is not definitive, you can always decide not to mentor\n> at all later for any reason as long as an intern has not been selected\n> yet. (Intern selection deadline is Nov. 9, 2020.)\n> \n"},{"id":"405996","messageId":"a9b7cac1-1993-dbf9-a048-a81c2c39a906@gmail.com","threadId":"54148","inReplyTo":"441bd08b-ca7d-5977-a455-c4c2a4bd4bc9@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2020-09-20T16:31:38Z","receivedAt":"2020-09-20T16:31:45Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 07-09-2020 00:26, Kaartic Sivaraam wrote:>\n>> I would appreciate help to find project ideas though. Are there still\n>> scripts that are worth converting to C (excluding git-bisect.sh and\n>> git-submodule.sh that are still worked on)? \n> \n> I think Dscho's e-mail linked below gives a nice overview of the various\n> scripts and their likely status as of Jan2020:\n> \n> https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n> \n> I'm guessing only the status of submodule has changed as it's being\n> worked on now.\n> \n\nAfter giving it a second thought, I believe I should take back my word\nabout the git-submodule status changing. There still seems to be some\nwork left for it. To be clear,\n\n- there's 'add', whose conversion is currently stalled [1]\n- there's 'update', which still has a decent amount of code [2]\n  in the shell script.\n- we still have to complete the conversion completely converting\n  moving the rest of the bits from `git-submodule.sh` to C which is\n  mostly just the option parsing. This might be more trickier than\n  it sounds as we would've to ensure the we don't accidentally\n  change behaviour of the options when moving the option parsing to C.\n\n  There's also an e-mail from Junio which is relevant [3]\n\nI'm not sure if this would be enough for a complete project on it's own.\nI'm also not sure whether 'add' would get converted in the meantime. In\nany case, I believe we could add a few other small refactoring projects\nto make up for the rest of the period. For instance,\n\n- Replace more instances of `the_index` and `the_repository`\n  (https://github.com/gitgitgadget/git/issues/379)\n\n- Turn the `fetch_if_missing` global into a field of `struct repository`\n  (https://github.com/gitgitgadget/git/issues/251)\n\n- Possibly others from #leftoverbits\n\nThoughts?\n\n\nReferences\n===\n[1]:\nhttp://public-inbox.org/git/20200824090359.403944-1-shouryashukla.oo@gmail.com/\n[2]: https://github.com/git/git/blob/v2.28.0/git-submodule.sh#L554-L713\n[3]: https://lore.kernel.org/git/xmqqtuzrrk8r.fsf@gitster.c.googlers.com/\n\n-- \nSivaraam\n"},{"id":"406011","messageId":"CAP8UFD05qPn6kGRTQGhwABvZbfoH3xcK3VpFo7d5koj9d7mUsg@mail.gmail.com","threadId":"54148","inReplyTo":"a9b7cac1-1993-dbf9-a048-a81c2c39a906@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-21T04:22:29Z","receivedAt":"2020-09-21T04:22:52Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sun, Sep 20, 2020 at 6:31 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> On 07-09-2020 00:26, Kaartic Sivaraam wrote:>\n> >> I would appreciate help to find project ideas though. Are there still\n> >> scripts that are worth converting to C (excluding git-bisect.sh and\n> >> git-submodule.sh that are still worked on)?\n> >\n> > I think Dscho's e-mail linked below gives a nice overview of the various\n> > scripts and their likely status as of Jan2020:\n> >\n> > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n> >\n> > I'm guessing only the status of submodule has changed as it's being\n> > worked on now.\n>\n> After giving it a second thought, I believe I should take back my word\n> about the git-submodule status changing. There still seems to be some\n> work left for it.\n\nYeah, there is some work left, but Shourya said he was interested in\ncontinuing to work on it.\n\n> To be clear,\n>\n> - there's 'add', whose conversion is currently stalled [1]\n\nYeah, but it hasn't been stalled for a long time, and sometimes it\ntakes time after the GSoC or Outreachy period for former GSoC students\nor Outreachy interns to resume their work.\n\n> - there's 'update', which still has a decent amount of code [2]\n>   in the shell script.\n> - we still have to complete the conversion completely converting\n>   moving the rest of the bits from `git-submodule.sh` to C which is\n>   mostly just the option parsing. This might be more trickier than\n>   it sounds as we would've to ensure the we don't accidentally\n>   change behaviour of the options when moving the option parsing to C.\n>\n>   There's also an e-mail from Junio which is relevant [3]\n>\n> I'm not sure if this would be enough for a complete project on it's own.\n> I'm also not sure whether 'add' would get converted in the meantime. In\n> any case, I believe we could add a few other small refactoring projects\n> to make up for the rest of the period. For instance,\n>\n> - Replace more instances of `the_index` and `the_repository`\n>   (https://github.com/gitgitgadget/git/issues/379)\n>\n> - Turn the `fetch_if_missing` global into a field of `struct repository`\n>   (https://github.com/gitgitgadget/git/issues/251)\n>\n> - Possibly others from #leftoverbits\n>\n> Thoughts?\n\nYeah, without 'add' we would have enough related issues for another\nproject. I would prefer though that we wait for at least 3 months\nwithout any progress before suggesting them as a project. That's what\nwe usually do and I think it's the right thing to do.\n"},{"id":"406013","messageId":"8b189b7d-e43f-a6fd-ff43-a02bca9e4132@gmail.com","threadId":"54148","inReplyTo":"CAP8UFD05qPn6kGRTQGhwABvZbfoH3xcK3VpFo7d5koj9d7mUsg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2020-09-21T07:59:19Z","receivedAt":"2020-09-21T08:00:12Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 21-09-2020 09:52, Christian Couder wrote:\n> On Sun, Sep 20, 2020 at 6:31 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n>>\n>> On 07-09-2020 00:26, Kaartic Sivaraam wrote:>\n>>>\n>>> I'm guessing only the status of submodule has changed as it's being\n>>> worked on now.\n>>\n>> After giving it a second thought, I believe I should take back my word\n>> about the git-submodule status changing. There still seems to be some\n>> work left for it.\n> \n> Yeah, there is some work left, but Shourya said he was interested in\n> continuing to work on it.\n> \n\nYeah, he's most welcome to resume his work :)\n\n>> To be clear,\n>>\n>> - there's 'add', whose conversion is currently stalled [1]\n> \n> Yeah, but it hasn't been stalled for a long time, and sometimes it\n> takes time after the GSoC or Outreachy period for former GSoC students\n> or Outreachy interns to resume their work.\n>\n\nOk. Got it.\n\n>> - there's 'update', which still has a decent amount of code [2]\n>>   in the shell script.\n>> - we still have to complete the conversion completely converting\n>>   moving the rest of the bits from `git-submodule.sh` to C which is\n>>   mostly just the option parsing. This might be more trickier than\n>>   it sounds as we would've to ensure the we don't accidentally\n>>   change behaviour of the options when moving the option parsing to C.\n>>\n>>   There's also an e-mail from Junio which is relevant [3]\n>>\n>> I'm not sure if this would be enough for a complete project on it's own.\n>> I'm also not sure whether 'add' would get converted in the meantime. In\n>> any case, I believe we could add a few other small refactoring projects\n>> to make up for the rest of the period. For instance,\n>>\n>> - Replace more instances of `the_index` and `the_repository`\n>>   (https://github.com/gitgitgadget/git/issues/379)\n>>\n>> - Turn the `fetch_if_missing` global into a field of `struct repository`\n>>   (https://github.com/gitgitgadget/git/issues/251)\n>>\n>> - Possibly others from #leftoverbits\n>>\n>> Thoughts?\n> \n> Yeah, without 'add' we would have enough related issues for another\n> project. I would prefer though that we wait for at least 3 months\n> without any progress before suggesting them as a project. That's what\n> we usually do and I think it's the right thing to do.\n> \n\nOk. That makes sense. I also missed the fact that Shourya had also\nexpressed interested in converting the 'update' part of submodule in his\nfinal GSoC report [A]. So, I agree that it's too early to propose the\nrest of the submodule work for Outreachy.\n\nThanks.\n\n\nReferences\n===\n[A]: https://shouryashukla.blogspot.com/2020/08/the-final-report.html\n\n--\nSivaraam\n"},{"id":"406070","messageId":"nycvar.QRO.7.76.6.2009201705060.5061@tvgsbejvaqbjf.bet","threadId":"54148","inReplyTo":"CAP8UFD1BxnOk4-gaUQb9bY5zhAtD8Jy-x0RC=pNMSQvUaVxRmg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2020-09-20T15:06:39Z","receivedAt":"2020-09-21T20:21:45Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Christian,\n\nOn Sat, 19 Sep 2020, Christian Couder wrote:\n\n> On Wed, Sep 16, 2020 at 10:27 PM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n>\n> > On Wed, 16 Sep 2020, Christian Couder wrote:\n>\n> > > To summarize more, it seems to me that only the following scripts\n> > > could be worth converting:\n> > >\n> > > git-difftool--helper.sh\n> > > git-mergetool--lib.sh\n> > > git-mergetool.sh\n> > >\n> > > I wonder if they are really worth converting though, as they should\n> > > probably all be converted together and we would likely also need to\n> > > convert the scripts in mergetools/ at the same time. And then there\n> > > should be a way to still easily configure things for users. So perhaps\n> > > a better way to approach this would be first to convert the scripts in\n> > > mergetools/ into config files.\n> >\n> > The biggest problem is that they're all entangled.\n> > `git-difftool--helper.sh` sources `git-mergetool--lib.sh` and uses quite a\n> > bit of its machinery.\n>\n> Yeah, I agree this is an issue.\n>\n> > As to converting the scripts to config files, I'd rather have them\n> > hard-coded in the source code.\n>\n> I am not sure what are the pros and cons of hardcoding vs config files\n> in this case.\n\nThe thing is: `make install` does not install a Git config. That's why I\nwant the defaults hard-coded.\n\nOf course, it should be possible to override those hard-coded defaults via\nthe config. That should go without saying.\n\nCiao,\nDscho\n\n> My opinion is that config files would make it easier for people to\n> contribute what's needed for new tools, while hardcoding might make it\n> more easily extensible for us and might reduce backward compatibility\n> issues.\n>\n> > I would then probably try to implement the bare minimum for the\n> > `difftool--helper` command to work (re-implementing in C only the parts of\n> > `mergetool--lib` that are necessary), and only in a next patch series work\n> > on `mergetool`.\n>\n> Thanks for your opinion on this. For now I think it needs to be\n> discussed more before we could suggest it as a project.\n>\n> Best,\n> Christian.\n>\n"},{"id":"406072","messageId":"CAP6+3T11vpwgJJZQwTC6vgp2+RzRS8fxLLyZrbFvt3=cmi8vyA@mail.gmail.com","threadId":"54148","inReplyTo":"CAP8UFD05qPn6kGRTQGhwABvZbfoH3xcK3VpFo7d5koj9d7mUsg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Shourya Shukla","fromEmail":"shouryashukla.oo@gmail.com","sentAt":"2020-09-21T20:56:28Z","receivedAt":"2020-09-21T20:56:41Z","isPatch":false,"sender":{"key":"shouryashukla.oo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43680618?v=4"},"body":"On Mon, Sep 21, 2020 at 9:52 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> On Sun, Sep 20, 2020 at 6:31 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n> >\n> > On 07-09-2020 00:26, Kaartic Sivaraam wrote:>\n> > >> I would appreciate help to find project ideas though. Are there still\n> > >> scripts that are worth converting to C (excluding git-bisect.sh and\n> > >> git-submodule.sh that are still worked on)?\n> > >\n> > > I think Dscho's e-mail linked below gives a nice overview of the various\n> > > scripts and their likely status as of Jan2020:\n> > >\n> > > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\n> > >\n> > > I'm guessing only the status of submodule has changed as it's being\n> > > worked on now.\n> >\n> > After giving it a second thought, I believe I should take back my word\n> > about the git-submodule status changing. There still seems to be some\n> > work left for it.\n>\n> Yeah, there is some work left, but Shourya said he was interested in\n> continuing to work on it.\n\nYeah, I am a bit busy right now catching up with the classes and assignments\nin my college. I will try to deliver a follow-up v2 to 'submodule add'\nin a couple\nof weeks.\n\n> > To be clear,\n> >\n> > - there's 'add', whose conversion is currently stalled [1]\n>\n> Yeah, but it hasn't been stalled for a long time, and sometimes it\n> takes time after the GSoC or Outreachy period for former GSoC students\n> or Outreachy interns to resume their work.\n>\n> > - there's 'update', which still has a decent amount of code [2]\n> >   in the shell script.\n> > - we still have to complete the conversion completely converting\n> >   moving the rest of the bits from `git-submodule.sh` to C which is\n> >   mostly just the option parsing. This might be more trickier than\n> >   it sounds as we would've to ensure the we don't accidentally\n> >   change behaviour of the options when moving the option parsing to C.\n> >\n> >   There's also an e-mail from Junio which is relevant [3]\n> >\n> > I'm not sure if this would be enough for a complete project on it's own.\n> > I'm also not sure whether 'add' would get converted in the meantime. In\n> > any case, I believe we could add a few other small refactoring projects\n> > to make up for the rest of the period. For instance,\n> >\n> > - Replace more instances of `the_index` and `the_repository`\n> >   (https://github.com/gitgitgadget/git/issues/379)\n> >\n> > - Turn the `fetch_if_missing` global into a field of `struct repository`\n> >   (https://github.com/gitgitgadget/git/issues/251)\n> >\n> > - Possibly others from #leftoverbits\n> >\n> > Thoughts?\n>\n> Yeah, without 'add' we would have enough related issues for another\n> project. I would prefer though that we wait for at least 3 months\n> without any progress before suggesting them as a project. That's what\n> we usually do and I think it's the right thing to do.\n\nIf we are talking about submodules, then one project can be to improve\nthe parsing of 'submodule--helper.c' and try to eliminate the shell scripting\nfor this purpose. Another thing which can be done is to clean up the helper\nsub-commands which were created to aid the conversion (iff they are of\nlittle to no use now). I do not have an exact idea if the \"improve parsing\" and\nconversion of a couple of subcommands* will be a project big enough\nfor Outreachy\nor not though.\n\n*'submodule update' is a bit messed up right now and will need a solid\nconversion\nto C since some of its fragments are there in the C code while some\naren't. Also, the shell\ncode of this subcommand is still there meaning that the fragments do\nnot play any direct role\nin the functioning of the subcommand. I can pass on the conversion of\n'update' to Outreachy\nif the addition of this will amount to a complete project for a\npotential Outreachy intern.\n\nRegards,\nShourya Shukla\n"},{"id":"406505","messageId":"c6367303-dc40-e896-4ed7-19f9d75b73df@gmail.com","threadId":"54148","inReplyTo":"CAP8UFD31B9YgninC2Fyb=0+OVY7E4SW7LGBbx9E7CrgSn+95BA@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2020-09-27T16:59:55Z","receivedAt":"2020-09-27T17:00:05Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 16-09-2020 14:31, Christian Couder wrote:\n> \n> - Accelerate rename detection and range-diff\n> (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> co-mentor with someone a bit familiar with the suggested algorithms.\n\nI just applied to be a co-mentor for this project. I'm not familiar with\nthe suggested algorithms right now but I hope I'll be able to get\nfamiliar with them over time. If someone else more suitable for the\nproject could volunteer, I wouldn't mind stepping aside :)\n\nThanks,\nSivaraam\n"},{"id":"406515","messageId":"CAP8UFD1Qvp010Ugd=CyEpYragy-t_xt0D8JbcB_4VHJMHf9F9w@mail.gmail.com","threadId":"54148","inReplyTo":"c6367303-dc40-e896-4ed7-19f9d75b73df@gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-09-27T21:16:16Z","receivedAt":"2020-09-27T21:16:34Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Kaartic,\n\nOn Sun, Sep 27, 2020 at 6:59 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> On 16-09-2020 14:31, Christian Couder wrote:\n> >\n> > - Accelerate rename detection and range-diff\n> > (https://github.com/gitgitgadget/git/issues/519): ideally I would\n> > co-mentor with someone a bit familiar with the suggested algorithms.\n>\n> I just applied to be a co-mentor for this project. I'm not familiar with\n> the suggested algorithms right now but I hope I'll be able to get\n> familiar with them over time. If someone else more suitable for the\n> project could volunteer, I wouldn't mind stepping aside :)\n\nThanks for volunteering!\n\nIn the meantime I have asked GitLab if they could fund one intern.\n\nBest,\nChristian.\n"},{"id":"408639","messageId":"CAP8UFD2OR0O-1d8bdaevxJWUgJpxYq-uky=eJHq-V=2DnyY38w@mail.gmail.com","threadId":"54148","inReplyTo":"CAP8UFD1Qvp010Ugd=CyEpYragy-t_xt0D8JbcB_4VHJMHf9F9w@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-10-29T10:13:30Z","receivedAt":"2020-10-29T10:13:45Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi everyone,\n\nOn Sun, Sep 27, 2020 at 11:16 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> In the meantime I have asked GitLab if they could fund one intern.\n\nGitLab approved funding one intern, so we now have funding for one\nintern for each of our 3 Outreachy projects. I updated the \"funding\"\ninformation related to Git on Outrachy's website accordingly.\n\nBest,\nChristian.\n"}]}