{"thread":{"id":"56433","subject":"Git in Outreachy?","startedAt":"2021-09-03T02:40:50Z","lastAt":"2021-09-29T20:30:52Z","messageCount":23,"participants":["Taylor Blau","Emily Shaffer","Christian Couder","ZheNing Hu","Jeff King","Matheus Tavares Bernardino"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"434620","messageId":"YTGLLQCvlnT17jo8@nand.local","threadId":"56433","inReplyTo":null,"subject":"Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"ttaylorr@github.com","sentAt":"2021-09-03T02:40:45Z","receivedAt":"2021-09-03T02:40:50Z","isPatch":false,"sender":{"key":"ttaylorr@github.com","avatar":"https://gravatar.com/avatar/d5f3476f26b6f99cbb6b467e7ed7482f5762c8157bc73f569196e428bdcbea25?d=mp&s=160"},"body":"Are we interested in participating in the December 2021 round of\nOutreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\napplication deadline.\n\nChristian, Peff, and I discussed off-list that we would each try to pull\ntogether funding for one intern from GitHub and GitLab respectively.\n\nIf we're interested, the project submission deadline is September 23rd\n[1]. By then, we'd need:\n\n - Volunteers to act as mentors\n\n - Updates to our applicant materials on git.github.io (project ideas,\n as well as potential microprojects).\n\nThanks,\nTaylor\n\n[1]: https://www.outreachy.org/docs/community/#current-timeline\n"},{"id":"434665","messageId":"CAJoAoZnHk9shE0D4UHVhd3zTqDBmOeCHvf0ukjEt5k5B6u=jcQ@mail.gmail.com","threadId":"56433","inReplyTo":"YTGLLQCvlnT17jo8@nand.local","subject":"Re: Git in Outreachy?","fromName":"Emily Shaffer","fromEmail":"emilyshaffer@google.com","sentAt":"2021-09-03T18:33:38Z","receivedAt":"2021-09-03T18:33:52Z","isPatch":false,"sender":{"key":"nasamuffin@google.com","avatar":"https://avatars.githubusercontent.com/u/1606826?v=4"},"body":"On Thu, Sep 2, 2021 at 7:41 PM Taylor Blau wrote:\n>\n> Are we interested in participating in the December 2021 round of\n> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> application deadline.\n>\n> Christian, Peff, and I discussed off-list that we would each try to pull\n> together funding for one intern from GitHub and GitLab respectively.\n>\n> If we're interested, the project submission deadline is September 23rd\n> [1]. By then, we'd need:\n>\n> - Volunteers to act as mentors\n\nI'd be happy to mentor actively during the application stage, but I\ndon't have bandwidth to host/mentor an accepted intern this term. I\nwould also be happy to be CC'd, pinged, and so on on any reviews from\ninterns which aren't receiving enough love.\n\n> - Updates to our applicant materials on git.github.io (project ideas,\n> as well as potential microprojects).\n\nWill bring this up with Google folks today and see if we've got any ideas.\n\nThanks for mentioning it, Taylor.\n"},{"id":"434676","messageId":"CAP8UFD2SNyCj6Weo4EeHt0Z-CW9CEJbQbzmU7jhwfJdNW9CrYQ@mail.gmail.com","threadId":"56433","inReplyTo":"YTGLLQCvlnT17jo8@nand.local","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-04T04:30:10Z","receivedAt":"2021-09-04T04:30:26Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Sep 3, 2021 at 4:40 AM Taylor Blau wrote:\n>\n> Are we interested in participating in the December 2021 round of\n> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> application deadline.\n>\n> Christian, Peff, and I discussed off-list that we would each try to pull\n> together funding for one intern from GitHub and GitLab respectively.\n\nYeah, and we submitted an initial community application.\n\n> If we're interested, the project submission deadline is September 23rd\n> [1]. By then, we'd need:\n>\n> - Volunteers to act as mentors\n\nI am ok with co-mentoring 2 interns.\n\n> - Updates to our applicant materials on git.github.io (project ideas,\n> as well as potential microprojects).\n\nAbout microprojects, I have been wondering if there are run_command*()\ncalls that could be replaced by direct calls to C functions like what\nJunio did in ffcb4e94d3 (bisect: do not run show-branch just to show\nthe current commit, 2021-07-27), and if that could make a good\nmicroproject.\n\nAbout project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\nref-filter formats with other \\-\\-pretty formats\" project could be and\nidea, though maybe it could interact too much with ZheNing Hu\ncontinuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\nproject.\n"},{"id":"434679","messageId":"CAOLTT8QufEU5Q64JfQyEOs4FYCsrNX2jgj8PdmYziVtKnRyu4w@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD2SNyCj6Weo4EeHt0Z-CW9CEJbQbzmU7jhwfJdNW9CrYQ@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-04T07:40:41Z","receivedAt":"2021-09-04T07:40:54Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Hi,\n\nChristian Couder 于2021年9月4日周六 下午12:30写道：\n>\n> On Fri, Sep 3, 2021 at 4:40 AM Taylor Blau wrote:\n> >\n> > Are we interested in participating in the December 2021 round of\n> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> > application deadline.\n> >\n> > Christian, Peff, and I discussed off-list that we would each try to pull\n> > together funding for one intern from GitHub and GitLab respectively.\n>\n> Yeah, and we submitted an initial community application.\n>\n> > If we're interested, the project submission deadline is September 23rd\n> > [1]. By then, we'd need:\n> >\n> > - Volunteers to act as mentors\n>\n> I am ok with co-mentoring 2 interns.\n>\n> > - Updates to our applicant materials on git.github.io (project ideas,\n> > as well as potential microprojects).\n>\n> About microprojects, I have been wondering if there are run_command*()\n> calls that could be replaced by direct calls to C functions like what\n> Junio did in ffcb4e94d3 (bisect: do not run show-branch just to show\n> the current commit, 2021-07-27), and if that could make a good\n> microproject.\n>\n> About project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\n> ref-filter formats with other \\-\\-pretty formats\" project could be and\n> idea, though maybe it could interact too much with ZheNing Hu\n> continuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\n> project.\n\nIf the project idea is related to Hariom or my GSoC project, I think I can\nprovide a lot of help. :) I can help them as a mentor.\n\nThis may be a place to promote my patches: See [1][2][3].\nIt can provide some extra atoms for git cat-file --batch | --batch-check,\nlike %(tree), %(author), %(tagger) etc. Although some performance\noptimizations have been made, It still has small performance gap.\n\nIf the community still expects git cat-file --batch to reuse the logic\nof ref-filter,\nI expect it to get the attention of reviewers.\n\nThe solutions I can think of to further optimize performance are:\n1. Delay the evaluation of some ref-filter intermediate data.\n2. Let ref-filter code reentrant and can be called in multi-threaded to take\nadvantage of multi-core.\nThese ideas may be very difficult to implement now.\n\n[1]: https://lore.kernel.org/git/CAOLTT8SxHuH2EbiSwQX6pyJJs5KyVuKx6ZOPxpzWLH+Tbz5F+A@mail.gmail.com/\n[2]: https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/\n[3]: https://github.com/adlternative/git/commits/cat-file-reuse-ref-filter-logic\n\nThanks.\n--\nZheNing Hu\n"},{"id":"434693","messageId":"YTNrehKnfPo3E5RI@coredump.intra.peff.net","threadId":"56433","inReplyTo":"CAOLTT8QufEU5Q64JfQyEOs4FYCsrNX2jgj8PdmYziVtKnRyu4w@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2021-09-04T12:50:02Z","receivedAt":"2021-09-04T12:50:05Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:\n\n> This may be a place to promote my patches: See [1][2][3].\n> It can provide some extra atoms for git cat-file --batch | --batch-check,\n> like %(tree), %(author), %(tagger) etc. Although some performance\n> optimizations have been made, It still has small performance gap.\n> \n> If the community still expects git cat-file --batch to reuse the logic\n> of ref-filter,\n> I expect it to get the attention of reviewers.\n> \n> The solutions I can think of to further optimize performance are:\n> 1. Delay the evaluation of some ref-filter intermediate data.\n> 2. Let ref-filter code reentrant and can be called in multi-threaded to take\n> advantage of multi-core.\n\nI don't think trying to thread it will help much. For expensive formats,\nwhere we have to actually open and parse objects, in theory we could do\nthat in parallel. But most of our time there is spent in zlib getting\nthe object data, and that all needs to be done under a big lock.\n\nFor little formats (e.g., just printing \"%(refname)\"), we need to\nserialize the output anyway. So our unit of work is so tiny, I suspect\nthat the threading overhead would be a net negative.\n\nI was coincidentally looking at ref-filter last week, and it seemed to\nme that a lot of the slowness is because of the over-use of malloc\n(e.g., we allocate a substring for every atom_value, and then form them\ninto a separate buffer). If we could parse the original format into a\nform that could be traversed without having to do further allocations,\njust writing directly to a strbuf (or even a file handle), I think that\nwould be a big improvement.\n\nI just posted the results of some of my experiments to the list:\n\n https://lore.kernel.org/git/YTNpQ7Od1U%2F5i0R7@coredump.intra.peff.net/\n\nI don't think that gives any kind of useful base to build on, but it\nshows what's possible by skipping past various segments of the\nref-filter code.\n\n-Peff\n"},{"id":"434702","messageId":"YTOyMxo2qZeBIWDM@nand.local","threadId":"56433","inReplyTo":"YTGLLQCvlnT17jo8@nand.local","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2021-09-04T17:51:47Z","receivedAt":"2021-09-04T17:51:52Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> - Updates to our applicant materials on git.github.io (project ideas,\n> as well as potential microprojects).\n\nOne project I have been thinking of is a grab-bag of bitmap-related\ntasks. Some ideas for general improvements are:\n\n - Designing a new .bitmap format (perhaps using the new chunkfile\n API?) to allow us to add optional data to it in the future, like any\n information we might need for a stable object order.\n\n - Experimenting with replacing EWAH with different bitmap compression\n algorithms to see if we can increase read performance and/or\n decrease file size.\n\n - Tidy up and take measurements from my RFC patch(es) to add an\n extension which indicates which commits have bitmaps, and at what\n position. These were discussed beginning at:\n\n https://lore.kernel.org/git/YNuiM8TR5evSeNsN@nand.local/\n\n (but they seem to help most when there isn't too much traversal\n required between the ref tips and the bitmapped commits).\n\n - Rethinking bitmap selection to be more robust against repositories\n which have \"spikey\" ref tips and for which follow-on traversal is\n expensive.\n\nThese are all fairly open-ended, and so may not make a good Outreachy\nproject. But I would be in favor of having more people familiar with and\ninterested in reachability bitmaps.\n\nI'll think of some others, too.\n\nThanks,\nTaylor\n"},{"id":"434722","messageId":"CAOLTT8S1Tfu6YWcoHhZcydQYd_yBBCavdqyV_TzoOrEW6zHXGQ@mail.gmail.com","threadId":"56433","inReplyTo":"YTNrehKnfPo3E5RI@coredump.intra.peff.net","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-05T08:58:57Z","receivedAt":"2021-09-05T08:59:12Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Jeff King 于2021年9月4日周六 下午8:50写道：\n>\n> On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:\n>\n> > This may be a place to promote my patches: See [1][2][3].\n> > It can provide some extra atoms for git cat-file --batch | --batch-check,\n> > like %(tree), %(author), %(tagger) etc. Although some performance\n> > optimizations have been made, It still has small performance gap.\n> >\n> > If the community still expects git cat-file --batch to reuse the logic\n> > of ref-filter,\n> > I expect it to get the attention of reviewers.\n> >\n> > The solutions I can think of to further optimize performance are:\n> > 1. Delay the evaluation of some ref-filter intermediate data.\n> > 2. Let ref-filter code reentrant and can be called in multi-threaded to take\n> > advantage of multi-core.\n>\n> I don't think trying to thread it will help much. For expensive formats,\n> where we have to actually open and parse objects, in theory we could do\n> that in parallel. But most of our time there is spent in zlib getting\n> the object data, and that all needs to be done under a big lock.\n>\n\nThis big lock is \"obj_read_lock()\", right? If there are indeed the limitations\nof these locks, I am afraid that the parallel scheme is not good.\n\n> For little formats (e.g., just printing \"%(refname)\"), we need to\n> serialize the output anyway. So our unit of work is so tiny, I suspect\n> that the threading overhead would be a net negative.\n>\n\nMake sence.\n\n> I was coincidentally looking at ref-filter last week, and it seemed to\n> me that a lot of the slowness is because of the over-use of malloc\n\nAgree. malloc() and data-copy is the reason for the poor performance of\nref-filter.\n\n> (e.g., we allocate a substring for every atom_value, and then form them\n> into a separate buffer). If we could parse the original format into a\n> form that could be traversed without having to do further allocations,\n> just writing directly to a strbuf (or even a file handle), I think that\n> would be a big improvement.\n>\n\nThis patch has been tried to eliminate some malloc and data-copy:\nhttps://lore.kernel.org/git/3760ff032bb1dec3812881fd408f8d78ec125477.1629184489.git.gitgitgadget@gmail.com/\nIt is indeed possible to obtain some optimizations.\n\n> I just posted the results of some of my experiments to the list:\n>\n> https://lore.kernel.org/git/YTNpQ7Od1U%2F5i0R7@coredump.intra.peff.net/\n>\n> I don't think that gives any kind of useful base to build on, but it\n> shows what's possible by skipping past various segments of the\n> ref-filter code.\n>\n> -Peff\n\nThanks.\n--\nZheNing Hu\n"},{"id":"434788","messageId":"CAHd-oW7PKQRQMRhG8577SKXL=tKSNCj=kavCthKLwZHWa-0n9w@mail.gmail.com","threadId":"56433","inReplyTo":"CAOLTT8S1Tfu6YWcoHhZcydQYd_yBBCavdqyV_TzoOrEW6zHXGQ@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Matheus Tavares Bernardino","fromEmail":"matheus.bernardino@usp.br","sentAt":"2021-09-06T12:36:31Z","receivedAt":"2021-09-06T12:36:46Z","isPatch":false,"sender":{"key":"matheus.tavb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12701583?v=4"},"body":"On Sun, Sep 5, 2021 at 5:59 AM ZheNing Hu wrote:\n>\n> Jeff King 于2021年9月4日周六 下午8:50写道：\n> >\n> > On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:\n> >\n> > > This may be a place to promote my patches: See [1][2][3].\n> > > It can provide some extra atoms for git cat-file --batch | --batch-check,\n> > > like %(tree), %(author), %(tagger) etc. Although some performance\n> > > optimizations have been made, It still has small performance gap.\n> > >\n> > > If the community still expects git cat-file --batch to reuse the logic\n> > > of ref-filter,\n> > > I expect it to get the attention of reviewers.\n> > >\n> > > The solutions I can think of to further optimize performance are:\n> > > 1. Delay the evaluation of some ref-filter intermediate data.\n> > > 2. Let ref-filter code reentrant and can be called in multi-threaded to take\n> > > advantage of multi-core.\n> >\n> > I don't think trying to thread it will help much. For expensive formats,\n> > where we have to actually open and parse objects, in theory we could do\n> > that in parallel. But most of our time there is spent in zlib getting\n> > the object data, and that all needs to be done under a big lock.\n>\n> This big lock is \"obj_read_lock()\", right?\n\nThe object reading code actually releases this lock before doing zlib\ndecompression (and acquires it right after), to allow better\nmulti-threaded performance.\n\nHowever, it is unfortunately not so simple to call object reading\nroutines in multi-threaded code, even with this lock. The lock mainly\nprotects `oid_object_info_extended()` and its wrappers. Some global\nresources used by these functions are also accessed outside of them,\nwhich could lead to race conditions in threaded code.\n\nThat's why `builtin/grep.c` and `grep.c` have some explicit calls to\n`obj_read_lock()` outside `object-file.c` and `packfile.c`. (And it\ncan be quite tricky to identity these cases.)\n"},{"id":"434817","messageId":"CAOLTT8Ra93pBzML4wD0mOOBSM+boG3aTgtWc9qsiBHTMZ0m+=g@mail.gmail.com","threadId":"56433","inReplyTo":"CAHd-oW7PKQRQMRhG8577SKXL=tKSNCj=kavCthKLwZHWa-0n9w@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-07T05:50:21Z","receivedAt":"2021-09-07T05:50:41Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Matheus Tavares Bernardino 于2021年9月6日周一 下午8:36写道：\n>\n> On Sun, Sep 5, 2021 at 5:59 AM ZheNing Hu wrote:\n> >\n> > Jeff King 于2021年9月4日周六 下午8:50写道：\n> > >\n> > > On Sat, Sep 04, 2021 at 03:40:41PM +0800, ZheNing Hu wrote:\n> > >\n> > > > This may be a place to promote my patches: See [1][2][3].\n> > > > It can provide some extra atoms for git cat-file --batch | --batch-check,\n> > > > like %(tree), %(author), %(tagger) etc. Although some performance\n> > > > optimizations have been made, It still has small performance gap.\n> > > >\n> > > > If the community still expects git cat-file --batch to reuse the logic\n> > > > of ref-filter,\n> > > > I expect it to get the attention of reviewers.\n> > > >\n> > > > The solutions I can think of to further optimize performance are:\n> > > > 1. Delay the evaluation of some ref-filter intermediate data.\n> > > > 2. Let ref-filter code reentrant and can be called in multi-threaded to take\n> > > > advantage of multi-core.\n> > >\n> > > I don't think trying to thread it will help much. For expensive formats,\n> > > where we have to actually open and parse objects, in theory we could do\n> > > that in parallel. But most of our time there is spent in zlib getting\n> > > the object data, and that all needs to be done under a big lock.\n> >\n> > This big lock is \"obj_read_lock()\", right?\n>\n> The object reading code actually releases this lock before doing zlib\n> decompression (and acquires it right after), to allow better\n> multi-threaded performance.\n>\n\nYeah, I guess this unlock place is in unpack_loose_short_header().\n\n> However, it is unfortunately not so simple to call object reading\n> routines in multi-threaded code, even with this lock. The lock mainly\n> protects `oid_object_info_extended()` and its wrappers. Some global\n> resources used by these functions are also accessed outside of them,\n> which could lead to race conditions in threaded code.\n>\n> That's why `builtin/grep.c` and `grep.c` have some explicit calls to\n> `obj_read_lock()` outside `object-file.c` and `packfile.c`. (And it\n> can be quite tricky to identity these cases.)\n\nIndeed, a large number of global variables in ref-filter code are worth\neliminating.\n\nThanks.\n--\nZheNing Hu\n"},{"id":"436314","messageId":"YUYPgF6tRQ5ERYWL@nand.local","threadId":"56433","inReplyTo":"YTGLLQCvlnT17jo8@nand.local","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2021-09-18T16:10:40Z","receivedAt":"2021-09-18T16:10:44Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"[+everybody from upthread to cc]\n\nOn Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> Are we interested in participating in the December 2021 round of\n> Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> application deadline.\n\nThe project deadline of September 23rd is fast approaching, and we do\nnot have any proposed projects or signed-up mentors.\n\nIf you are interested in mentoring, the time to sign-up and propose a\nproject is definitely ASAP :-). You can do so by clicking \"Submit a\nproject proposal\" at:\n\n https://www.outreachy.org/communities/cfp/git/\n\nThanks,\nTaylor\n"},{"id":"436403","messageId":"CAOLTT8SbS9-grLnn2TOL6XdR3yMkd=YrUnq=FLCo6r03Fqbg9A@mail.gmail.com","threadId":"56433","inReplyTo":"YUYPgF6tRQ5ERYWL@nand.local","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-20T07:45:17Z","receivedAt":"2021-09-20T07:45:33Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Taylor Blau 于2021年9月19日周日 上午12:10写道：\n>\n> [+everybody from upthread to cc]\n>\n> On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> > Are we interested in participating in the December 2021 round of\n> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> > application deadline.\n>\n> The project deadline of September 23rd is fast approaching, and we do\n> not have any proposed projects or signed-up mentors.\n>\n> If you are interested in mentoring, the time to sign-up and propose a\n> project is definitely ASAP :-). You can do so by clicking \"Submit a\n> project proposal\" at:\n>\n> https://www.outreachy.org/communities/cfp/git/\n>\n\nI haven't thought of any good projects for the time being,\nChristian, any ideas?\n\n> Thanks,\n> Taylor\n\nThanks.\n--\nZheNing Hu\n"},{"id":"436419","messageId":"CAP8UFD37tQdbcgsMJPYE7KaO1ajwznFRUrG=9=S1WNNM-YZsqw@mail.gmail.com","threadId":"56433","inReplyTo":"CAOLTT8SbS9-grLnn2TOL6XdR3yMkd=YrUnq=FLCo6r03Fqbg9A@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-20T14:52:38Z","receivedAt":"2021-09-20T14:52:54Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu wrote:\n>\n> Taylor Blau 于2021年9月19日周日 上午12:10写道：\n> >\n> > [+everybody from upthread to cc]\n> >\n> > On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> > > Are we interested in participating in the December 2021 round of\n> > > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> > > application deadline.\n> >\n> > The project deadline of September 23rd is fast approaching, and we do\n> > not have any proposed projects or signed-up mentors.\n> >\n> > If you are interested in mentoring, the time to sign-up and propose a\n> > project is definitely ASAP :-). You can do so by clicking \"Submit a\n> > project proposal\" at:\n> >\n> > https://www.outreachy.org/communities/cfp/git/\n>\n> I haven't thought of any good projects for the time being,\n> Christian, any ideas?\n\nI already suggested the following project upthread:\n\n> > About project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\n> > ref-filter formats with other \\-\\-pretty formats\" project could be and\n> > idea, though maybe it could interact too much with ZheNing Hu\n> > continuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\n> > project.\n\nand you replied:\n\n> If the project idea is related to Hariom or my GSoC project, I think I can\n> provide a lot of help. :) I can help them as a mentor.\n\nso I am ok to co-mentor this project with you.\n\nIf you are still ok, I will submit it.\n\nI will also prepare soon a page with a few micro-projects. Of course\nmore micro-project and regular project ideas are very welcome!\n"},{"id":"436422","messageId":"CAP8UFD2SsZyckX0tpCN-16BJ_mX6iHgd+VNSvfr-kirq2knVyg@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD37tQdbcgsMJPYE7KaO1ajwznFRUrG=9=S1WNNM-YZsqw@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-20T15:15:14Z","receivedAt":"2021-09-20T15:15:29Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Sep 20, 2021 at 4:52 PM Christian Couder\n wrote:\n\n> I will also prepare soon a page with a few micro-projects. Of course\n> more micro-project and regular project ideas are very welcome!\n\nSo here is the page:\n\nhttps://git.github.io/Outreachy-23-Microprojects/\n\nIt's very similar as last year's page\n(https://git.github.io/Outreachy-21-Microprojects/). The differences\nare:\n\n- added new \"Replace a run_command*() call by direct calls to C functions\" idea\n- removed \"Unify the meaning of -dirty between diff and describe\" idea\nas it looks a bit complex for a micro-project (though I can add it\nback if someone disagree with this opinion).\n"},{"id":"436572","messageId":"CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD37tQdbcgsMJPYE7KaO1ajwznFRUrG=9=S1WNNM-YZsqw@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-21T05:39:42Z","receivedAt":"2021-09-21T05:39:56Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Christian Couder 于2021年9月20日周一 下午10:52写道：\n>\n> On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu wrote:\n> >\n> > Taylor Blau 于2021年9月19日周日 上午12:10写道：\n> > >\n> > > [+everybody from upthread to cc]\n> > >\n> > > On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> > > > Are we interested in participating in the December 2021 round of\n> > > > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> > > > application deadline.\n> > >\n> > > The project deadline of September 23rd is fast approaching, and we do\n> > > not have any proposed projects or signed-up mentors.\n> > >\n> > > If you are interested in mentoring, the time to sign-up and propose a\n> > > project is definitely ASAP :-). You can do so by clicking \"Submit a\n> > > project proposal\" at:\n> > >\n> > > https://www.outreachy.org/communities/cfp/git/\n> >\n> > I haven't thought of any good projects for the time being,\n> > Christian, any ideas?\n>\n> I already suggested the following project upthread:\n>\n> > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\n> > > ref-filter formats with other \\-\\-pretty formats\" project could be and\n> > > idea, though maybe it could interact too much with ZheNing Hu\n> > > continuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\n> > > project.\n>\n> and you replied:\n>\n> > If the project idea is related to Hariom or my GSoC project, I think I can\n> > provide a lot of help. :) I can help them as a mentor.\n>\n> so I am ok to co-mentor this project with you.\n>\n> If you are still ok, I will submit it.\n>\n\nYeah, I am ok. grateful.\n\n> I will also prepare soon a page with a few micro-projects. Of course\n> more micro-project and regular project ideas are very welcome!\n\nI am still looking at the code in ref-filter.c these two days, I deeply\ndoubt whether we can add a --no-sort option to git for-each-ref,\n\nInspired by Peff's experimental patches [1], I think the --no-sort option\nmay improve the performance of ref-filter by avoiding the execution\nof ref_array_sort().\n\nI don't know if this can be regarded as a micro-project.\n\nThis may require the help of this patch of mine: [2]\nwhich use list api for ref_sorting. This may can help eliminate unnecessary\nsorting.\n\n[1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/\n[2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/\n\nThanks.\n--\nZheNing Hu\n"},{"id":"436574","messageId":"CAOLTT8SACMz_Tct_W+_kh_cG2ELcg7c2sQ=S2si3zpiwDcZSLg@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD2SsZyckX0tpCN-16BJ_mX6iHgd+VNSvfr-kirq2knVyg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-21T05:41:05Z","receivedAt":"2021-09-21T05:41:19Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Christian Couder 于2021年9月20日周一 下午11:15写道：\n>\n> On Mon, Sep 20, 2021 at 4:52 PM Christian Couder\n> wrote:\n>\n> > I will also prepare soon a page with a few micro-projects. Of course\n> > more micro-project and regular project ideas are very welcome!\n>\n> So here is the page:\n>\n> https://git.github.io/Outreachy-23-Microprojects/\n>\n\ns/Outreachy-23-Microprojects/Outreachy-22-Microprojects/\n\n> It's very similar as last year's page\n> (https://git.github.io/Outreachy-21-Microprojects/). The differences\n> are:\n>\n> - added new \"Replace a run_command*() call by direct calls to C functions\" idea\n> - removed \"Unify the meaning of -dirty between diff and describe\" idea\n> as it looks a bit complex for a micro-project (though I can add it\n> back if someone disagree with this opinion).\n"},{"id":"436622","messageId":"CAP8UFD0xjUWK7B82xEerX4e_pkZ-BATKwjNcEjg4AxB4mipL1g@mail.gmail.com","threadId":"56433","inReplyTo":"CAOLTT8S8TxuTmddGp2WGoPtTc3gwGXzizBfVzKd87otRw7Dpiw@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-21T15:35:04Z","receivedAt":"2021-09-21T15:35:19Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Sep 21, 2021 at 7:39 AM ZheNing Hu wrote:\n>\n> Christian Couder 于2021年9月20日周一 下午10:52写道：\n> >\n> > On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu wrote:\n\n> > > I haven't thought of any good projects for the time being,\n> > > Christian, any ideas?\n> >\n> > I already suggested the following project upthread:\n> >\n> > > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\n> > > > ref-filter formats with other \\-\\-pretty formats\" project could be and\n> > > > idea, though maybe it could interact too much with ZheNing Hu\n> > > > continuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\n> > > > project.\n> >\n> > and you replied:\n> >\n> > > If the project idea is related to Hariom or my GSoC project, I think I can\n> > > provide a lot of help. :) I can help them as a mentor.\n> >\n> > so I am ok to co-mentor this project with you.\n> >\n> > If you are still ok, I will submit it.\n>\n> Yeah, I am ok. grateful.\n\nI submitted it. You should see it and be able to register as a co-mentor there:\n\nhttps://www.outreachy.org/communities/cfp/git/\n\n> I am still looking at the code in ref-filter.c these two days, I deeply\n> doubt whether we can add a --no-sort option to git for-each-ref,\n>\n> Inspired by Peff's experimental patches [1], I think the --no-sort option\n> may improve the performance of ref-filter by avoiding the execution\n> of ref_array_sort().\n>\n> I don't know if this can be regarded as a micro-project.\n\nIf you think that such a patch is likely to be accepted and that would\ntake you less than a few hours to prepare and submit, then it can\nprobably be regarded as a micro-project, and you are welcome to send a\npull request to add it to the micro-project page.\n\n> This may require the help of this patch of mine: [2]\n> which use list api for ref_sorting. This may can help eliminate unnecessary\n> sorting.\n>\n> [1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/\n> [2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/\n\nThen please add this information to the description of the micro-project.\n\nThanks!\n"},{"id":"436623","messageId":"CAP8UFD01CNqK+-M1nnHU05WP3kW7pdXvjcgJFg1GopAt8ucQ-g@mail.gmail.com","threadId":"56433","inReplyTo":"CAOLTT8SACMz_Tct_W+_kh_cG2ELcg7c2sQ=S2si3zpiwDcZSLg@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-21T15:39:31Z","receivedAt":"2021-09-21T15:39:44Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Sep 21, 2021 at 7:41 AM ZheNing Hu wrote:\n>\n> Christian Couder 于2021年9月20日周一 下午11:15写道：\n> >\n> > On Mon, Sep 20, 2021 at 4:52 PM Christian Couder\n> > wrote:\n> >\n> > > I will also prepare soon a page with a few micro-projects. Of course\n> > > more micro-project and regular project ideas are very welcome!\n> >\n> > So here is the page:\n> >\n> > https://git.github.io/Outreachy-23-Microprojects/\n> >\n>\n> s/Outreachy-23-Microprojects/Outreachy-22-Microprojects/\n\nI think the number is not linked to the year but rather to the number\nof Outreachy rounds since the beginning.\n\nLast year's Winter round was round 21 and there has been a Summer\nround we didn't participate in, so I think the Winter 2021-2022 is\nround 23.\n\nBut yeah, it might be clearer to rename all the Outreachy files with\nnames like Outreachy-Winter-21-22-Microprojects to avoid such\nconfusion, as I think the round number is not used much anymore by\nanyone.\n"},{"id":"436671","messageId":"YUpN4zrZmyxoTb4l@nand.local","threadId":"56433","inReplyTo":"YUYPgF6tRQ5ERYWL@nand.local","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2021-09-21T21:25:55Z","receivedAt":"2021-09-21T21:26:04Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Sat, Sep 18, 2021 at 12:10:40PM -0400, Taylor Blau wrote:\n> On Thu, Sep 02, 2021 at 10:40:45PM -0400, Taylor Blau wrote:\n> > Are we interested in participating in the December 2021 round of\n> > Outreachy? September 3rd (tomorrow at 4pm UTC) is the initial community\n> > application deadline.\n>\n> The project deadline of September 23rd is fast approaching, and we do\n> not have any proposed projects or signed-up mentors.\n\nIt looks like the deadline was extended to September 29th at 4pm UTC. So\nwe have a little less than an extra week. The below link is still the\nright place to submit proposals:\n\n https://www.outreachy.org/communities/cfp/git/\n\nThanks,\nTaylor\n"},{"id":"436726","messageId":"CAOLTT8TQj==048r3poLcWHpy=duma26odK=ZxZdtWSOVfdZ5+w@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD0xjUWK7B82xEerX4e_pkZ-BATKwjNcEjg4AxB4mipL1g@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-22T14:58:53Z","receivedAt":"2021-09-22T14:59:11Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Christian Couder 于2021年9月21日周二 下午11:35写道：\n>\n> On Tue, Sep 21, 2021 at 7:39 AM ZheNing Hu wrote:\n> >\n> > Christian Couder 于2021年9月20日周一 下午10:52写道：\n> > >\n> > > On Mon, Sep 20, 2021 at 9:45 AM ZheNing Hu wrote:\n>\n> > > > I haven't thought of any good projects for the time being,\n> > > > Christian, any ideas?\n> > >\n> > > I already suggested the following project upthread:\n> > >\n> > > > > About project ideas, maybe continuing Hariom Verma's GSoC 2020 \"Unify\n> > > > > ref-filter formats with other \\-\\-pretty formats\" project could be and\n> > > > > idea, though maybe it could interact too much with ZheNing Hu\n> > > > > continuing his GSoC 2021 \"Use ref-filter formats in `git cat-file`\"\n> > > > > project.\n> > >\n> > > and you replied:\n> > >\n> > > > If the project idea is related to Hariom or my GSoC project, I think I can\n> > > > provide a lot of help. :) I can help them as a mentor.\n> > >\n> > > so I am ok to co-mentor this project with you.\n> > >\n> > > If you are still ok, I will submit it.\n> >\n> > Yeah, I am ok. grateful.\n>\n> I submitted it. You should see it and be able to register as a co-mentor there:\n>\n> https://www.outreachy.org/communities/cfp/git/\n>\n\nYes, I saw it. Thanks!\n\n> > I am still looking at the code in ref-filter.c these two days, I deeply\n> > doubt whether we can add a --no-sort option to git for-each-ref,\n> >\n> > Inspired by Peff's experimental patches [1], I think the --no-sort option\n> > may improve the performance of ref-filter by avoiding the execution\n> > of ref_array_sort().\n> >\n> > I don't know if this can be regarded as a micro-project.\n>\n> If you think that such a patch is likely to be accepted and that would\n> take you less than a few hours to prepare and submit, then it can\n> probably be regarded as a micro-project, and you are welcome to send a\n> pull request to add it to the micro-project page.\n>\n\nEh, It may not be simple, I can try to solve it by myself first, but I\nthink it is\nappropriate for novices to complete this mini-project to understand the\ntechnical details of ref-filter.\n\n> > This may require the help of this patch of mine: [2]\n> > which use list api for ref_sorting. This may can help eliminate unnecessary\n> > sorting.\n> >\n> > [1] https://lore.kernel.org/git/YTTC2IUO1ZmTOEoR@coredump.intra.peff.net/\n> > [2] https://lore.kernel.org/git/pull.1025.git.1629882532.gitgitgadget@gmail.com/\n>\n> Then please add this information to the description of the micro-project.\n>\n\nok!\n\n> Thanks!\n\nThanks.\n--\nZheNing Hu\n"},{"id":"436727","messageId":"CAOLTT8RL_HnEQ4WPrq-KpBRLKjexroxtz0SVAFZYakF2AXY7jw@mail.gmail.com","threadId":"56433","inReplyTo":"CAP8UFD01CNqK+-M1nnHU05WP3kW7pdXvjcgJFg1GopAt8ucQ-g@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-22T15:01:00Z","receivedAt":"2021-09-22T15:01:20Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Christian Couder 于2021年9月21日周二 下午11:39写道：\n>\n> On Tue, Sep 21, 2021 at 7:41 AM ZheNing Hu wrote:\n> >\n> > Christian Couder 于2021年9月20日周一 下午11:15写道：\n> > >\n> > > On Mon, Sep 20, 2021 at 4:52 PM Christian Couder\n> > > wrote:\n> > >\n> > > > I will also prepare soon a page with a few micro-projects. Of course\n> > > > more micro-project and regular project ideas are very welcome!\n> > >\n> > > So here is the page:\n> > >\n> > > https://git.github.io/Outreachy-23-Microprojects/\n> > >\n> >\n> > s/Outreachy-23-Microprojects/Outreachy-22-Microprojects/\n>\n> I think the number is not linked to the year but rather to the number\n> of Outreachy rounds since the beginning.\n>\n> Last year's Winter round was round 21 and there has been a Summer\n> round we didn't participate in, so I think the Winter 2021-2022 is\n> round 23.\n>\n\nOk. I thought it was related to the year before.\n\n> But yeah, it might be clearer to rename all the Outreachy files with\n> names like Outreachy-Winter-21-22-Microprojects to avoid such\n> confusion, as I think the round number is not used much anymore by\n> anyone.\n\nThanks.\n--\nZheNing Hu\n"},{"id":"437459","messageId":"CAP8UFD0snuPE0L+L2LxEgCAQXaP_j9LwxwJP_ZounOtg4kRv_g@mail.gmail.com","threadId":"56433","inReplyTo":"YUpN4zrZmyxoTb4l@nand.local","subject":"Re: Git in Outreachy?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2021-09-29T14:18:43Z","receivedAt":"2021-09-29T14:18:58Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Taylor and all,\n\nOn Tue, Sep 21, 2021 at 11:26 PM Taylor Blau wrote:\n\n> > The project deadline of September 23rd is fast approaching, and we do\n> > not have any proposed projects or signed-up mentors.\n>\n> It looks like the deadline was extended to September 29th at 4pm UTC. So\n> we have a little less than an extra week. The below link is still the\n> right place to submit proposals:\n>\n> https://www.outreachy.org/communities/cfp/git/\n\nSo the deadline for mentors to submit projects has been extended again\nto Wednesday, October 6 at 4pm UTC.\n\nWe still have only one project (\"Unify ref-filter formats with other\npretty formats\", that ZheNing and me are willing to co-mentor)\nsubmitted though.\n\nI plan to submit another project that I will be willing to (co-)mentor\nbefore the deadline.\n\nIt's confirmed that GitLab will sponsor one intern.\n\nBest,\nChristian.\n"},{"id":"437471","messageId":"YVSjkMLdxtURP5iN@nand.local","threadId":"56433","inReplyTo":"CAP8UFD0snuPE0L+L2LxEgCAQXaP_j9LwxwJP_ZounOtg4kRv_g@mail.gmail.com","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2021-09-29T17:34:08Z","receivedAt":"2021-09-29T17:34:12Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Wed, Sep 29, 2021 at 04:18:43PM +0200, Christian Couder wrote:\n> Hi Taylor and all,\n>\n> On Tue, Sep 21, 2021 at 11:26 PM Taylor Blau wrote:\n>\n> > > The project deadline of September 23rd is fast approaching, and we do\n> > > not have any proposed projects or signed-up mentors.\n> >\n> > It looks like the deadline was extended to September 29th at 4pm UTC. So\n> > we have a little less than an extra week. The below link is still the\n> > right place to submit proposals:\n> >\n> > https://www.outreachy.org/communities/cfp/git/\n>\n> So the deadline for mentors to submit projects has been extended again\n> to Wednesday, October 6 at 4pm UTC.\n\nThanks for mentioning. I got an email from Sage announcing this\nyesterday, but neglected to share it here.\n\n> We still have only one project (\"Unify ref-filter formats with other\n> pretty formats\", that ZheNing and me are willing to co-mentor)\n> submitted though.\n\nI plan to submit and mentor a project myself. (I'm thinking that I'll do\na grab-bag of bitmap-related items that I'd like to see implemented, but\nthat may be too open-ended for a successful Outreachy project).\n\nGitHub is planning on sponsoring an intern, too, but I haven't finalized\nthe paperwork.\n\nThanks,\nTaylor\n"},{"id":"437479","messageId":"YVTM+WQH/UyhVeTz@nand.local","threadId":"56433","inReplyTo":"YVSjkMLdxtURP5iN@nand.local","subject":"Re: Git in Outreachy?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2021-09-29T20:30:49Z","receivedAt":"2021-09-29T20:30:52Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Wed, Sep 29, 2021 at 01:34:08PM -0400, Taylor Blau wrote:\n> > We still have only one project (\"Unify ref-filter formats with other\n> > pretty formats\", that ZheNing and me are willing to co-mentor)\n> > submitted though.\n>\n> I plan to submit and mentor a project myself. (I'm thinking that I'll do\n> a grab-bag of bitmap-related items that I'd like to see implemented, but\n> that may be too open-ended for a successful Outreachy project).\n\nI think (open-ended as it may be) that I'll be able to provide the most\nguidance for a bitmap-related project. I submitted that as a intern\nproject, which anybody logged in through the Outreachy site can view\nhere:\n\n https://www.outreachy.org/apply/project-selection/#git\n\nThanks,\nTaylor\n"}]}