[GSoC] Info: git log --oneline improvements

Hi Christian and Johannes,

I will like to send another proposal on git log --oneline improvements. My first proposal[1] was on "Convert scripts to builtins". Can you provide me information about "git log --online improvements" and point me to resources where I should focus on my proposal.

[1]: https://public-inbox.org/git/20180321061605.27814-1-predatoramigo@gmail.com/

Cheers, Pratik Karki

Hi,

On Sat, Mar 24, 2018 at 5:32 AM, Pratik Karki <predatoramigo@gmail.com> wrote:

On the Idea page (https://git.github.io/SoC-2018-Ideas/) there are the following links:

https://public-inbox.org/git/xmqqeg42fslw.fsf@gitster.mtv.corp.google.com/T/#t http://public-inbox.org/git/CA+55aFwT2HUBzZO8Gpt9tHoJtdRxv9oe3TDoSH5jcEOixRNBXg@mail.gmail.com/

so a good idea to start writing a proposal would be to summarize the possible improvements that are discussed in these threads.

Thanks.

Hi Christian and Johannes,

Though I sent a mail earlier, saying I would like to submit another proposal, I am now skeptical on re-writing another proposal as you guys are only available mentor for GSoC and I believe Git doesn't select more than 2 proposals. Hence, I will try to update my previous proposal[1] and make it more worthy. Can you review it and explain what I might be lacking there? Thank you for your time.

[1]: https://public-inbox.org/git/20180321061605.27814-1-predatoramigo@gmail.com/

Cheers, Pratik Karki

Hi,

On Sat, Mar 24, 2018 at 9:41 AM, Pratik Karki <predatoramigo@gmail.com> wrote:

Well Stefan Beller wrote in

https://public-inbox.org/git/CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com/

that he would be ok to co-mentor, but I am not sure which projects he would be ok to co-mentor. I just Cc'ed him so he can tell us more.

Yeah, because mentoring is a lot of work, and doesn't always work out as well as we would expect, (mostly because it is difficult to explain to new contributors that review cycles for significant patch series take a lot more time than they could imagine), so not many people volunteer to mentor or co-mentor.

I still hope though that over time some former GSoC student will become (co-)mentors as this happens quite often in other projects that participates in the GSoC.

Best, Christian.

On Sat, Mar 24, 2018 at 4:15 AM Christian Couder <christian.couder@gmail.com> wrote:

wrote:

Is there a place/email where I can read up on the git log --oneline improvements? I use the --oneline flag a lot and would be interested in hearing what you plan there.

https://public-inbox.org/git/CAGZ79kax5Hip1wP3U60im__Dm0GvH8nNd+ByxG5OxMXrRkRvdQ@mail.gmail.com/

I would be happy to co mentor any project by prioritizing some review time on it.

Regarding rewriting shell scripts in C, there have been GSoC students in the previous years, which may help you understand the scope of the project better.

     git clone --mirror https://public-inbox.org/git
     git clone https://git.kernel.org/pub/scm/git/git.git/

and search via "git log --author=" for Paul Tan, who converted git-am and git-pull into C or Prathamesh Chavan, who rewrote git-submodule to be in C, but the result is not upstream (yet).

I think there are more shell to C conversions, but I was involved with these 2, hence giving these examples.

I agree on this. Mentoring takes some time as well. The coding part is the easy part, the communication part with the community is the harder part.

For example the Git community is spread across all time zones. So if you want to give everyone the opportunity to give input to your patches you want to wait 2 hours.

The community consists of people with diverse backgrounds, e.g. some work on Git in their spare time on the weekends [only]. Others work on it as their job [so it is rather a Mon-Fri activity]; others glance at the mailing list in the lunch break or in the evenings.

These timing issues are not the hardest part, but the easiest to explain shortly. ;)