{"thread":{"id":"62229","subject":"[Outreachy]","startedAt":"2024-10-02T03:04:45Z","lastAt":"2024-10-08T09:40:19Z","messageCount":8,"participants":["Abraham Samuel","Phillip Wood","Patrick Steinhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"503884","messageId":"CAO1n884e13_9FZDBtcFrwU8oCyv+0_WUT-c16qN0W9c+D6k2PQ@mail.gmail.com","threadId":"62229","inReplyTo":null,"subject":"[Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-02T03:04:34Z","receivedAt":"2024-10-02T03:04:45Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and\neager to start making valuable contributions to this project. Thanks\n"},{"id":"503931","messageId":"834250ef-46ec-4667-8e41-e427472fd623@gmail.com","threadId":"62229","inReplyTo":"CAO1n884e13_9FZDBtcFrwU8oCyv+0_WUT-c16qN0W9c+D6k2PQ@mail.gmail.com","subject":"Re: [Outreachy]","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2024-10-02T14:04:06Z","receivedAt":"2024-10-02T14:04:09Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"Hi Abraham\n\nOn 02/10/2024 04:04, Abraham Samuel wrote:\n> Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and\n> eager to start making valuable contributions to this project. Thanks\n\nHappy to hear that you are interested in contributing to Git as part of\nthe Outreachy projet. To help us mentors, could you please clarify which\nof the two approved projects you are interested in?\n\nOther than that I would strongly recommend reading through [1] and [2],\nif you haven't already done so. They should give you some ideas for how\nthe Outreachy application process is designed to work in the Git project\nand lays out the expectation of us mentors.\n\nLet me know in case you have any additional questions.\n\nPhillip\n\n[1]: https://git.github.io/Mentoring-Program-Guide/\n[2]: https://git.github.io/General-Microproject-Information/\n\n"},{"id":"504012","messageId":"CAO1n887uu5qUcqLcdKfh8FBKJAQUCGqVOnAzX7WWiFEnuuMF3A@mail.gmail.com","threadId":"62229","inReplyTo":"834250ef-46ec-4667-8e41-e427472fd623@gmail.com","subject":"Re: [Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-03T02:14:08Z","receivedAt":"2024-10-03T02:14:19Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"Hello Philip, thanks for your prompt response. As regards your\nrequest, I want to work on the project description 'Convert unit tests\nto use the clar testing framework'.\n\nOn Wed, Oct 2, 2024 at 3:04 PM Phillip Wood wrote:\n>\n> Hi Abraham\n>\n> On 02/10/2024 04:04, Abraham Samuel wrote:\n> > Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and\n> > eager to start making valuable contributions to this project. Thanks\n>\n> Happy to hear that you are interested in contributing to Git as part of\n> the Outreachy projet. To help us mentors, could you please clarify which\n> of the two approved projects you are interested in?\n>\n> Other than that I would strongly recommend reading through [1] and [2],\n> if you haven't already done so. They should give you some ideas for how\n> the Outreachy application process is designed to work in the Git project\n> and lays out the expectation of us mentors.\n>\n> Let me know in case you have any additional questions.\n>\n> Phillip\n>\n> [1]: https://git.github.io/Mentoring-Program-Guide/\n> [2]: https://git.github.io/General-Microproject-Information/\n>\n"},{"id":"504175","messageId":"CAO1n887hN81j5h12t-6xpNQAQ5uOx1wxLz48c+O4hZE-pWdY8A@mail.gmail.com","threadId":"62229","inReplyTo":"CAO1n887uu5qUcqLcdKfh8FBKJAQUCGqVOnAzX7WWiFEnuuMF3A@mail.gmail.com","subject":"Re: [Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-06T09:57:26Z","receivedAt":"2024-10-06T09:57:37Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"Hi Philip,\nI have read through [1], [2] and other articles relevant to completing\na micro project and contributing to git. After going through the\nmicroproject ideas, I have come up with two possible projects I am\ninterested in working on.\n1. changing the style for 'cd' in the test subshell.\nIn this following email,\nhttps://lore.kernel.org/git/CAPig+cQpUu2UO-+jWn1nTaDykWnxwuEitzVB7PnW2SS_b7V8Hg@mail.gmail.com/\nIt explains how to modernise and clean up t7001, and example of which is\n\n* style for `cd` in subshell is:\n\n (\n cd foo &&\n ...\n ) &&\n\n not:\n\n (cd foo &&\n ...\n\n ) &&.\nHowever, a sample outdated style can be seen in the sample file\nt/t5605-clone-local.sh which I would like to work on to change those\ninstances to the modern accepted code style\nSome examples can be seen in the file as follows.\ntest_expect_success 'local clone without .git suffix' '\ngit clone -l -s a b &&\n(cd b &&\necho false >expect &&\ngit config --bool core.bare >actual &&\ntest_cmp expect actual &&\ngit fetch)\n'\ntest_expect_success 'local clone with .git suffix' '\ngit clone -l -s a.git c &&\n(cd c && git fetch)\n'\ntest_expect_success 'bundle clone with nonexistent HEAD (match default)' '\ngit clone b2.bundle b2 &&\n(cd b2 &&\ngit fetch &&\ngit rev-parse --verify refs/heads/main)\n'\n\n2. Use test_path_is_* functions in test scripts.\nI have found three potential test files in the t/ directory\nt5601-clone.sh\ntest_expect_success 'clone --mirror' '\n\ngit clone --mirror src mirror &&\ntest -f mirror/HEAD &&\ntest ! -f mirror/file &&\nFETCH=\"$(cd mirror && git config remote.origin.fetch)\" &&\ntest \"+refs/*:refs/*\" = \"$FETCH\" &&\nMIRROR=\"$(cd mirror && git config --bool remote.origin.mirror)\" &&\ntest \"$MIRROR\" = true\n\n'\n\nt7300-clean.sh\ntest_expect_success 'git clean with skip-worktree .gitignore' '\ngit update-index --skip-worktree .gitignore &&\nrm .gitignore &&\nmkdir -p build docs &&\ntouch a.out src/part3.c docs/manual.txt obj.o build/lib.so &&\ngit clean &&\ntest -f Makefile &&\ntest -f README &&\ntest -f src/part1.c &&\ntest -f src/part2.c &&\ntest ! -f a.out &&\ntest ! -f src/part3.c &&\ntest -f docs/manual.txt &&\ntest -f obj.o &&\ntest -f build/lib.so &&\ngit update-index --no-skip-worktree .gitignore &&\ngit checkout .gitignore\n'\nt7611-merge-abort.sh\ntest_expect_success 'fails without MERGE_HEAD (completed merge)' '\ngit merge clean_branch &&\ntest ! -f .git/MERGE_HEAD &&\n# Merge successfully completed\npost_merge_head=\"$(git rev-parse HEAD)\" &&\ntest_must_fail git merge --abort 2>output &&\ntest_grep MERGE_HEAD output\n'\n\nThese tests can be refactored to use the test_path_is_file and\ntest_path_is_missing functions.\n\nPlease kindly let me know the possibility of doing these microprojects.\nThanks\nAbraham.\nOn Thu, Oct 3, 2024 at 3:14 AM Abraham Samuel wrote:\n>\n> Hello Philip, thanks for your prompt response. As regards your\n> request, I want to work on the project description 'Convert unit tests\n> to use the clar testing framework'.\n>\n> On Wed, Oct 2, 2024 at 3:04 PM Phillip Wood wrote:\n> >\n> > Hi Abraham\n> >\n> > On 02/10/2024 04:04, Abraham Samuel wrote:\n> > > Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and\n> > > eager to start making valuable contributions to this project. Thanks\n> >\n> > Happy to hear that you are interested in contributing to Git as part of\n> > the Outreachy projet. To help us mentors, could you please clarify which\n> > of the two approved projects you are interested in?\n> >\n> > Other than that I would strongly recommend reading through [1] and [2],\n> > if you haven't already done so. They should give you some ideas for how\n> > the Outreachy application process is designed to work in the Git project\n> > and lays out the expectation of us mentors.\n> >\n> > Let me know in case you have any additional questions.\n> >\n> > Phillip\n> >\n> > [1]: https://git.github.io/Mentoring-Program-Guide/\n> > [2]: https://git.github.io/General-Microproject-Information/\n> >\n"},{"id":"504247","messageId":"ZwNx-sKJJNDQ4sIC@pks.im","threadId":"62229","inReplyTo":"CAO1n887hN81j5h12t-6xpNQAQ5uOx1wxLz48c+O4hZE-pWdY8A@mail.gmail.com","subject":"Re: [Outreachy]","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-10-07T05:30:42Z","receivedAt":"2024-10-07T05:30:48Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi Abraham,\n\nOn Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:\n> Hi Philip,\n\none note up front: we tend to not top-post on this mailing list. The\nreply to an email should either go below the quoted parts, or if you\nwant to reply to multiple parts of the mail you can provide your answers\ninline like I do here.\n\n[snip]\n> Please kindly let me know the possibility of doing these microprojects.\n> Thanks\n\nAll of the examples you picked seem valid. You do not require something\nlike approval to work on those projects, but it would be nice to check\nthat there are no concurrent threads on the Git mailing list that handle\nthe same microprojects. I'm not aware of any though, so please feel free\nto pick any one of your proposals and work on it.\n\nThanks!\n\nPatrick\n"},{"id":"504326","messageId":"CAO1n885B-gcWFb1foA27OjWX8_mHQ=sKebZVbhvewwis7vRR0g@mail.gmail.com","threadId":"62229","inReplyTo":"CAO1n886ANrTzz2S=P4MT15WEeSSDFv+7+uBTsJ5MtXV5rgTu9w@mail.gmail.com","subject":"Re: [Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-07T13:25:33Z","receivedAt":"2024-10-07T13:25:43Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"On Mon, Oct 7, 2024 at 2:24 PM Abraham Samuel wrote:\n>\n>\n>\n>\n> On Mon, 7 Oct 2024, 06:30 Patrick Steinhardt, wrote:\n>>\n>> Hi Abraham,\n>>\n>> On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:\n>> > Hi Philip,\n>>\n>> one note up front: we tend to not top-post on this mailing list. The\n>> reply to an email should either go below the quoted parts, or if you\n>> want to reply to multiple parts of the mail you can provide your answers\n>> inline like I do here.\n>\n>\n> Okay thank you very much Patrick, I apologise for the mistake. I will take that into account\n>>\n>>\n>> [snip]\n>> > Please kindly let me know the possibility of doing these microprojects.\n>> > Thanks\n>>\n>> All of the examples you picked seem valid. You do not require something\n>> like approval to work on those projects, but it would be nice to check\n>> that there are no concurrent threads on the Git mailing list that handle\n>> the same microprojects. I'm not aware of any though, so please feel free\n>> to pick any one of your proposals and work on it.\n>>\n>> Thanks!\n>>\n>> Patrick.\n"},{"id":"504349","messageId":"CAO1n885jtQag_2gHkuVFggBH444vKCK2chuxfecvniuN7SMBMA@mail.gmail.com","threadId":"62229","inReplyTo":"ZwNx-sKJJNDQ4sIC@pks.im","subject":"Re: [Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-07T18:48:00Z","receivedAt":"2024-10-07T18:48:13Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"On Mon, Oct 7, 2024 at 6:30 AM Patrick Steinhardt wrote:\n>\n> Hi Abraham,\n>\n> On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:\n> > Hi Philip,\n>\n> one note up front: we tend to not top-post on this mailing list. The\n> reply to an email should either go below the quoted parts, or if you\n> want to reply to multiple parts of the mail you can provide your answers\n> inline like I do here.\n>\n> [snip]\n> > Please kindly let me know the possibility of doing these microprojects.\n> > Thanks\n>\n> All of the examples you picked seem valid. You do not require something\n> like approval to work on those projects, but it would be nice to check\n> that there are no concurrent threads on the Git mailing list that handle\n> the same microprojects. I'm not aware of any though, so please feel free\n> to pick any one of your proposals and work on it.\n>\n> Thanks!\n>\n> Patrick\n\nThank you very much Patrick, I appreciate your time. Please I hope I\nam replying the correct way this time.\nI have created a pull request on GitGitGadget, please can someone\nkindly allow me. Here is the link to the pull request\nhttps://github.com/gitgitgadget/git/pull/1811.\nThank you.\n"},{"id":"504409","messageId":"CAO1n885jXKXDWzzO2ncCeyfTGHh9i-_CfPSYMvt1DHbF_BP=uw@mail.gmail.com","threadId":"62229","inReplyTo":"CAO1n885jtQag_2gHkuVFggBH444vKCK2chuxfecvniuN7SMBMA@mail.gmail.com","subject":"Re: [Outreachy]","fromName":"Abraham Samuel","fromEmail":"sammymore50@gmail.com","sentAt":"2024-10-08T09:40:09Z","receivedAt":"2024-10-08T09:40:19Z","isPatch":false,"sender":{"key":"sammymore50@gmail.com","avatar":null},"body":"On Mon, Oct 7, 2024 at 7:48 PM Abraham Samuel wrote:\n>\n> On Mon, Oct 7, 2024 at 6:30 AM Patrick Steinhardt wrote:\n> >\n> > Hi Abraham,\n> >\n> > On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:\n> > > Hi Philip,\n> >\n> > one note up front: we tend to not top-post on this mailing list. The\n> > reply to an email should either go below the quoted parts, or if you\n> > want to reply to multiple parts of the mail you can provide your answers\n> > inline like I do here.\n> >\n> > [snip]\n> > > Please kindly let me know the possibility of doing these microprojects.\n> > > Thanks\n> >\n> > All of the examples you picked seem valid. You do not require something\n> > like approval to work on those projects, but it would be nice to check\n> > that there are no concurrent threads on the Git mailing list that handle\n> > the same microprojects. I'm not aware of any though, so please feel free\n> > to pick any one of your proposals and work on it.\n> >\n> > Thanks!\n> >\n> > Patrick\n>\n> Thank you very much Patrick, I appreciate your time. Please I hope I\n> am replying the correct way this time.\n> I have created a pull request on GitGitGadget, please can someone\n> kindly allow me. Here is the link to the pull request\n> https://github.com/gitgitgadget/git/pull/1811.\n> Thank you.\n\nHi Patrick,\nPlease I submitted this patch via gitgitgadget from my email\n\nhttps://lore.kernel.org/git/pull.1811.git.1728328755490.gitgitgadget@gmail.com/.\nMy github account uses a different email address\n to the one I applied to outreachy\n. How wanted to draw your attention to the\npatch because gitgitgadet did not include the [Outreachy] tag I added\nto the title and the patch title does not show the [Outreachy] tag in\nthe mail list.\nThanks for your time\n"}]}