From: Christian Couder <christian.couder@gmail.com>
To: Pratik Karki <predatoramigo@gmail.com>
Cc: git <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Stefan Beller <sbeller@google.com>
Subject: Re: [GSoC] Re: Info: git log --oneline improvements
Date: Sat, 24 Mar 2018 12:15:27 +0100 [thread overview]
Message-ID: <CAP8UFD3Q26oiusO-+0SyFd=J+DTnrL5Xemrk+LLOk3hAUEVe9Q@mail.gmail.com> (raw)
In-Reply-To: <20180324084103.3367-1-predatoramigo@gmail.com>
Hi,
On Sat, Mar 24, 2018 at 9:41 AM, Pratik Karki <predatoramigo@gmail.com> wrote:
>
> 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
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.
> and I believe Git doesn't
> select more than 2 proposals.
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.
next prev parent reply other threads:[~2018-03-24 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 4:32 [GSoC] Info: git log --oneline improvements Pratik Karki
2018-03-24 7:50 ` Christian Couder
2018-03-24 8:41 ` [GSoC] " Pratik Karki
2018-03-24 11:15 ` Christian Couder [this message]
2018-03-26 18:33 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3Q26oiusO-+0SyFd=J+DTnrL5Xemrk+LLOk3hAUEVe9Q@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=predatoramigo@gmail.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).