git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Paul Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
Cc: git <git@vger.kernel.org>, Yash Yadav <yashdimpu@gmail.com>,
	Alban Gruin <alban.gruin@gmail.com>
Subject: Re: [GSoC] Regarding "Convert scripts to builtins"
Date: Tue, 20 Mar 2018 00:41:13 +0100	[thread overview]
Message-ID: <CAP8UFD2j71GJsnrd8y=Wj3a+TrX6UQePOZXE1LFFiqjd3_a-0w@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD0aQxSZVRfOHUP80H+677zoNWPU1pdg7v4Qk+gKXCG8eg@mail.gmail.com>

On Tue, Mar 20, 2018 at 12:11 AM, Christian Couder
<christian.couder@gmail.com> wrote:
> On Sun, Mar 18, 2018 at 11:15 PM, Paul Sebastian Ungureanu
>> First of all, I find it difficult to pick which scripts would benefit
>> the most by being rewritten. I am thinking of git bisect, git stash
>> and git rebase since these are maybe some of the most popular commands
>> of Git. However, on the other side, scripts like
>> git-rebase--interactive.sh and git-bisect.sh are also subject of other
>> GSoC projects. Should I steer away from these projects or can I
>> consider them?
>
> If you are interested in converting these scripts, you should probably
> ask publicly to the former GSoC students who have been working on
> these projects if they still plan to continue working on them of if
> they are ok to let you finish/continue their work. You will get extra
> bonus points if they agree to help you or maybe co-mentor you.

I realize that you were perhaps talking about other potential GSoC
students who are also writing proposals about converting one of these
scripts. If you care about the other proposals though, you should
probably just write two proposals as we will have at most 2 GSoC
students this year. Just try to have different possible mentors
interested in your 2 proposals.

  reply	other threads:[~2018-03-19 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 22:15 [GSoC] Regarding "Convert scripts to builtins" Paul Sebastian Ungureanu
2018-03-19 23:11 ` Christian Couder
2018-03-19 23:41   ` Christian Couder [this message]
2018-03-21 12:32 ` Johannes Schindelin
2018-03-21 19:17   ` Wink Saville
2018-03-22 17:32     ` Johannes Schindelin
2018-03-22 17:50       ` Wink Saville
2018-03-23  9:48         ` Johannes Schindelin

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='CAP8UFD2j71GJsnrd8y=Wj3a+TrX6UQePOZXE1LFFiqjd3_a-0w@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=alban.gruin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ungureanupaulsebastian@gmail.com \
    --cc=yashdimpu@gmail.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).