From: Christian Couder <firstname.lastname@example.org> To: Chinmoy Chakraborty <email@example.com> Cc: git <firstname.lastname@example.org>, Bagas Sanjaya <email@example.com> Subject: Re: [GSoC] Draft Proposal (Convert submodule to builtin) Date: Fri, 2 Apr 2021 08:31:50 +0200 [thread overview] Message-ID: <CAP8UFD1PC=vQCXLLoECPzFc8BGGfQxptHE5+Et11F-=3-twZYg@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, Apr 2, 2021 at 7:44 AM Bagas Sanjaya <email@example.com> wrote: > > On 01/04/21 18.40, Chinmoy Chakraborty wrote: > > Greetings mentors, > > > > This is my draft proposal for the GSoC project, Convert submodule to builtin. > > > > It would be really helpful if you could review the draft and present your > > > > views on it :). Thanks for letting us know about your proposal! > > Link: https://github.com/chinmoy12c/GSoC/blob/master/GSoC_Git_proposal.pdf [...] > Anyway, I copy-pasted the quotation above from your proposal in PDF format. > but when I pasted it into text-only mail, it looks rather ugly. > So next time when sending GSoC proposal for Git, I would like to see > proposals in Markdown format (as well as PDF) for the reason above. I agree that proposals should be sent to the mailing list in a textual format inline. It's ok if you also send a link to a better formatted version of your proposal, so that people who prefer to read the better formatted version can do so. It's ok too, of course, if the final version uploaded into the GSoC web site is the better formatted version. Sending the textual version to the mailing list inline could make it easier for people who want to comment and discuss it, like patches are, which will help you make a better proposal. Later it might also help people searching the mailing list. Best, Christian.
next prev parent reply other threads:[~2021-04-02 6:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 11:40 Chinmoy Chakraborty 2021-04-02 5:32 ` Bagas Sanjaya 2021-04-02 6:31 ` Christian Couder [this message] 2021-04-02 7:05 ` Chinmoy Chakraborty 2021-04-03 14:14 ` Chinmoy Chakraborty 2021-04-05 14:44 ` Christian Couder 2021-04-06 19:53 ` Chinmoy Chakraborty 2021-04-08 9:11 ` Chinmoy Chakraborty 2021-04-10 12:03 ` Christian Couder 2021-04-02 7:04 ` Chinmoy Chakraborty
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='CAP8UFD1PC=vQCXLLoECPzFc8BGGfQxptHE5+Et11F-=3-twZYg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GSoC] Draft Proposal (Convert submodule to builtin)' \ /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
Code repositories for project(s) associated with this 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).