From: Christian Couder <christian.couder@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Git Community <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
Emily Shaffer <emilyshaffer@google.com>,
Atharva Raykar <raykar.ath@gmail.com>,
ZheNing Hu <adlternative@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Git in GSoC 2022?
Date: Thu, 27 Jan 2022 10:44:09 +0100 [thread overview]
Message-ID: <CAP8UFD38WDwMKf3tMKGt6hMxmsuZk2JkDRJaOZsXFqHvbVLRLQ@mail.gmail.com> (raw)
In-Reply-To: <9d2e58ab-2d8f-0797-84ed-0c1e8941edaa@gmail.com>
On Thu, Jan 27, 2022 at 4:55 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 27/01/22 01.29, Kaartic Sivaraam wrote:
> > - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
> > but both were picked by GSoC students the previous year. So,
> > we would need new ones this year.
>
> I have several project ideas:
>
> - Document the "binary diff" format. Right now we have documentation
> for all diff formats used in Git, except for binary diff. Hint:
> read `diff.c`
It seems a bit small as a project idea. Also we usually propose code
related projects. It might be a good one for Google Season of Docs
though:
https://developers.google.com/season-of-docs/
But I don't think we have ever participated in it.
> - Rewrite `git-request-pull.sh` in C. Currently the shell script
> implementation hard-codes message template and only outputs to
> stdout (though can be redirected to a file using shell means).
> In the C version, message template can be configured (with the
> default is same as current version) and introduces new
> `-o/--output` option to specify output file.
In https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/
Dscho put this script in the "Probably better to leave them as shell
scripts" category, so you might want to explain a bit more what would
be the benefits of converting it. Also would you be interested in
mentoring or co-mentoring a GSoC student working on this?
Thanks!
next prev parent reply other threads:[~2022-01-27 9:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27 9:32 ` Christian Couder
2022-01-29 18:09 ` Kaartic Sivaraam
2022-02-13 13:35 ` Christian Couder
2022-02-15 20:34 ` Kaartic Sivaraam
2022-02-15 23:18 ` Hariom verma
2022-02-16 15:40 ` Christian Couder
2022-02-17 15:07 ` Hariom verma
2022-02-17 17:18 ` Kaartic Sivaraam
2022-02-18 2:14 ` Hariom verma
2022-02-26 20:29 ` Kaartic Sivaraam
2022-02-28 11:03 ` Christian Couder
2022-02-28 18:02 ` Kaartic Sivaraam
2022-03-01 13:51 ` Christian Couder
2022-03-04 18:34 ` Kaartic Sivaraam
2022-01-27 3:55 ` Bagas Sanjaya
2022-01-27 9:44 ` Christian Couder [this message]
[not found] ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36 ` Kaartic Sivaraam
2022-03-09 11:49 ` Johannes Schindelin
2022-03-09 19:57 ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19 ` Kaartic Sivaraam
2022-02-02 17:42 ` Derrick Stolee
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43 ` Kaartic Sivaraam
2022-02-03 14:12 ` Philip Oakley
2022-02-12 18:12 ` Kaartic Sivaraam
2022-02-13 9:33 ` Christian Couder
2022-02-15 15:05 ` Philip Oakley
2022-02-15 20:32 ` Kaartic Sivaraam
2022-02-16 15:55 ` Christian Couder
2022-02-17 17:28 ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50 ` Derrick Stolee
2022-03-07 22:25 ` Hariom verma
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=CAP8UFD38WDwMKf3tMKGt6hMxmsuZk2JkDRJaOZsXFqHvbVLRLQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adlternative@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.com \
--cc=raykar.ath@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).