From: Christian Couder <christian.couder@gmail.com> To: Thomas Gummerer <t.gummerer@gmail.com> Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git <git@vger.kernel.org>, Jeff King <peff@peff.net>, SZEDER Gábor <szeder.dev@gmail.com>, Оля Тележная <olyatelezhnaya@gmail.com>, Matthieu Moy <Matthieu.Moy@gmail.com> Subject: Re: GSoC 2019: Git's application submitted Date: Tue, 12 Feb 2019 00:58:38 +0100 Message-ID: <CAP8UFD3s3-mR528FqV3yuMEZBqT0uP+Mp5hGDcN_a1LfAsR0bg@mail.gmail.com> (raw) In-Reply-To: <20190211221827.GG6085@hank.intra.tgummerer.com> On Mon, Feb 11, 2019 at 11:18 PM Thomas Gummerer <t.gummerer@gmail.com> wrote: > > On 02/11, Christian Couder wrote: > > Historically though we have always been very optimistic in what we > > thought a student could accomplish in a GSoC. And we are very likely > > to find more ideas for improvements during the GSoC, in case > > everything is "finished" before the end. I actually think that it has > > never happened that a student both "finished" the project before the > > end, and that no idea for improvement on top of the work was found. > > Fair enough. I think there's still a number of things that could do > with some refactoring in 'builtin/stash.c', e.g. use more of the > libgit.a API, instead of using the run_command API, or potentially > other improvements that could be made. > > Another thing that may be useful to do is to write down some actual > technical documentation on the format of what a stash commit looks > like. Yeah, using more of the libgit.a API, instead of the run_command API, and writing technical documentation on the stash commit format look like good ideas to me. I think I will add those items to the project description if you don't mind. > > So after all if you are willing to co-mentor such a project, I would > > be ok to co-mentor it with you, and we should add it to the list. > > Ok, I'll submit a PR to add it to the list. Great! I merged your PR. I also resurrected the "Convert scripts to builtins" idea as I think there might still be shell scripts that could be converted, like perhaps git-merge-octopus.sh, git-merge-one-file.sh and git-merge-resolve.sh. So I think we should be good regarding Google requirements. Thanks, Christian.
next prev parent reply index Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-04 9:16 Christian Couder [not found] ` <CAL21Bm=K6zZ=APkiP3A_X7xVoOfx-MY2435YMp5y1ztE-xyYtg@mail.gmail.com> 2019-02-04 12:54 ` Christian Couder 2019-02-04 21:52 ` Thomas Gummerer 2019-02-05 21:17 ` Thomas Gummerer 2019-02-05 22:00 ` Christian Couder 2019-02-06 22:09 ` Thomas Gummerer 2019-02-07 19:39 ` Johannes Schindelin 2019-02-07 21:33 ` Thomas Gummerer 2019-02-11 5:41 ` Оля Тележная 2019-02-11 7:45 ` Christian Couder 2019-02-11 8:31 ` Оля Тележная 2019-02-11 10:52 ` Christian Couder 2019-02-13 22:36 ` Elijah Newren 2019-02-14 9:48 ` Christian Couder 2019-02-11 8:35 ` Christian Couder 2019-02-11 22:18 ` Thomas Gummerer 2019-02-11 23:58 ` Christian Couder [this message] 2019-02-12 20:25 ` Thomas Gummerer 2019-02-12 20:49 ` Christian Couder 2019-02-12 22:13 ` Thomas Gummerer 2019-02-06 12:27 ` Johannes Schindelin 2019-03-05 12:04 ` Duy Nguyen 2019-03-05 12:23 ` Duy Nguyen 2019-03-06 4:49 ` Jeff King 2019-03-06 9:36 ` Duy Nguyen 2019-03-06 19:08 ` Jeff King 2019-03-06 14:16 ` Johannes Schindelin 2019-03-18 12:51 ` Duy Nguyen 2019-03-18 16:37 ` Christian Couder
Reply instructions: You may reply publically 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=CAP8UFD3s3-mR528FqV3yuMEZBqT0uP+Mp5hGDcN_a1LfAsR0bg@mail.gmail.com \ --to=christian.couder@gmail.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=Matthieu.Moy@gmail.com \ --cc=git@vger.kernel.org \ --cc=olyatelezhnaya@gmail.com \ --cc=peff@peff.net \ --cc=szeder.dev@gmail.com \ --cc=t.gummerer@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
git@vger.kernel.org list mirror (unofficial, one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Example config snippet for mirrors Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/public-inbox.git