{"thread":{"id":"48130","subject":"[GSoC] Info: git log --oneline improvements","startedAt":"2018-03-24T04:32:21Z","lastAt":"2018-03-26T18:33:16Z","messageCount":5,"participants":["Pratik Karki","Christian Couder","Stefan Beller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"342721","messageId":"20180324043205.31976-1-predatoramigo@gmail.com","threadId":"48130","inReplyTo":null,"subject":"[GSoC] Info: git log --oneline improvements","fromName":"Pratik Karki","fromEmail":"predatoramigo@gmail.com","sentAt":"2018-03-24T04:32:05Z","receivedAt":"2018-03-24T04:32:21Z","isPatch":false,"sender":{"key":"predatoramigo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12194950?v=4"},"body":"\nHi Christian and Johannes,\n\nI will like to send another proposal on git log --oneline improvements.\nMy first proposal[1] was on \"Convert scripts to builtins\". Can\nyou provide me information about \"git log --online improvements\"\nand point me to resources where I should focus on my proposal.\n\n\n\n[1]: https://public-inbox.org/git/20180321061605.27814-1-predatoramigo@gmail.com/\n\nCheers,\nPratik Karki\n"},{"id":"342805","messageId":"CAP8UFD2D-XU=YeJD7A+9wauu0WKHwkXgVxbEBkOGPyZE7GiOZA@mail.gmail.com","threadId":"48130","inReplyTo":"20180324043205.31976-1-predatoramigo@gmail.com","subject":"Re: [GSoC] Info: git log --oneline improvements","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2018-03-24T07:50:43Z","receivedAt":"2018-03-24T07:50:49Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Sat, Mar 24, 2018 at 5:32 AM, Pratik Karki <predatoramigo@gmail.com> wrote:\n>\n> Hi Christian and Johannes,\n>\n> I will like to send another proposal on git log --oneline improvements.\n> My first proposal[1] was on \"Convert scripts to builtins\". Can\n> you provide me information about \"git log --online improvements\"\n> and point me to resources where I should focus on my proposal.\n\nOn the Idea page (https://git.github.io/SoC-2018-Ideas/) there are the\nfollowing links:\n\nhttps://public-inbox.org/git/xmqqeg42fslw.fsf@gitster.mtv.corp.google.com/T/#t\nhttp://public-inbox.org/git/CA+55aFwT2HUBzZO8Gpt9tHoJtdRxv9oe3TDoSH5jcEOixRNBXg@mail.gmail.com/\n\nso a good idea to start writing a proposal would be to summarize the\npossible improvements that are discussed in these threads.\n\nThanks.\n"},{"id":"342807","messageId":"20180324084103.3367-1-predatoramigo@gmail.com","threadId":"48130","inReplyTo":"CAP8UFD2D-XU=YeJD7A+9wauu0WKHwkXgVxbEBkOGPyZE7GiOZA@mail.gmail.com","subject":"[GSoC] Re: Info: git log --oneline improvements","fromName":"Pratik Karki","fromEmail":"predatoramigo@gmail.com","sentAt":"2018-03-24T08:41:03Z","receivedAt":"2018-03-24T08:41:28Z","isPatch":false,"sender":{"key":"predatoramigo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12194950?v=4"},"body":"\nHi Christian and Johannes,\n\nThough I sent a mail earlier, saying I would like to submit another\nproposal, I am now skeptical on re-writing another proposal as you\nguys are only available mentor for GSoC and I believe Git doesn't\nselect more than 2 proposals. Hence, I will try to update my previous\nproposal[1] and make it more worthy. Can you review it and explain\nwhat I might be lacking there? Thank you for your time.\n\n\n[1]: https://public-inbox.org/git/20180321061605.27814-1-predatoramigo@gmail.com/\n\nCheers,\nPratik Karki\n"},{"id":"342814","messageId":"CAP8UFD3Q26oiusO-+0SyFd=J+DTnrL5Xemrk+LLOk3hAUEVe9Q@mail.gmail.com","threadId":"48130","inReplyTo":"20180324084103.3367-1-predatoramigo@gmail.com","subject":"Re: [GSoC] Re: Info: git log --oneline improvements","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2018-03-24T11:15:27Z","receivedAt":"2018-03-24T11:15:33Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Sat, Mar 24, 2018 at 9:41 AM, Pratik Karki <predatoramigo@gmail.com> wrote:\n>\n> Hi Christian and Johannes,\n>\n> Though I sent a mail earlier, saying I would like to submit another\n> proposal, I am now skeptical on re-writing another proposal as you\n> guys are only available mentor for GSoC\n\nWell Stefan Beller wrote in\n\nhttps://public-inbox.org/git/CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com/\n\nthat he would be ok to co-mentor, but I am not sure which projects he\nwould be ok to co-mentor. I just Cc'ed him so he can tell us more.\n\n> and I believe Git doesn't\n> select more than 2 proposals.\n\nYeah, because mentoring is a lot of work, and doesn't always work out\nas well as we would expect, (mostly because it is difficult to explain\nto new contributors that review cycles for significant patch series\ntake a lot more time than they could imagine), so not many people\nvolunteer to mentor or co-mentor.\n\nI still hope though that over time some former GSoC student will\nbecome (co-)mentors as this happens quite often in other projects that\nparticipates in the GSoC.\n\nBest,\nChristian.\n"},{"id":"343047","messageId":"CAGZ79kapp-k5NY+Zop78r+2VtxC+Qs-SBK75r3S6T78EAg4q+g@mail.gmail.com","threadId":"48130","inReplyTo":"CAP8UFD3Q26oiusO-+0SyFd=J+DTnrL5Xemrk+LLOk3hAUEVe9Q@mail.gmail.com","subject":"Re: [GSoC] Re: Info: git log --oneline improvements","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2018-03-26T18:33:00Z","receivedAt":"2018-03-26T18:33:16Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Sat, Mar 24, 2018 at 4:15 AM Christian Couder\n<christian.couder@gmail.com>\nwrote:\n\n> Hi,\n\n> On Sat, Mar 24, 2018 at 9:41 AM, Pratik Karki <predatoramigo@gmail.com>\nwrote:\n> >\n> > Hi Christian and Johannes,\n> >\n> > Though I sent a mail earlier, saying I would like to submit another\n> > proposal, I am now skeptical on re-writing another proposal as you\n> > guys are only available mentor for GSoC\n\nIs there a place/email where I can read up on the git log --oneline\nimprovements? I use the --oneline flag a lot and would be interested\nin hearing what you plan there.\n\n> Well Stefan Beller wrote in\n\n\nhttps://public-inbox.org/git/CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com/\n\n> that he would be ok to co-mentor, but I am not sure which projects he\n> would be ok to co-mentor. I just Cc'ed him so he can tell us more.\n\nI would be happy to co mentor any project by prioritizing some\nreview time on it.\n\nRegarding rewriting shell scripts in C,\nthere have been GSoC students in the previous years, which may help you\nunderstand the scope of the project better.\n\n     git clone --mirror https://public-inbox.org/git\n     git clone https://git.kernel.org/pub/scm/git/git.git/\n\nand search via \"git log --author=\" for\nPaul Tan, who converted git-am and git-pull into C\nor Prathamesh Chavan, who rewrote git-submodule\nto be in C, but the result is not upstream (yet).\n\nI think there are more shell to C conversions, but I was involved\nwith these 2, hence giving these examples.\n\n> > and I believe Git doesn't\n> > select more than 2 proposals.\n\n> Yeah, because mentoring is a lot of work, and doesn't always work out\n> as well as we would expect, (mostly because it is difficult to explain\n> to new contributors that review cycles for significant patch series\n> take a lot more time than they could imagine), so not many people\n> volunteer to mentor or co-mentor.\n\nI agree on this. Mentoring takes some time as well.\nThe coding part is the easy part, the communication part with\nthe community is the harder part.\n\nFor example the Git community is spread across all time zones.\nSo if you want to give everyone the opportunity to give input to\nyour patches you want to wait 2 hours.\n\nThe community consists of people with diverse backgrounds, e.g.\nsome work on Git in their spare time on the weekends [only]. Others\nwork on it as their job [so it is rather a Mon-Fri activity]; others glance\nat the mailing list in the lunch break or in the evenings.\n\nThese timing issues are not the hardest part,\nbut the easiest to explain shortly. ;)\n\n> I still hope though that over time some former GSoC student will\n> become (co-)mentors as this happens quite often in other projects that\n> participates in the GSoC.\n"}]}