From: Christian Couder <email@example.com> To: Hariom verma <firstname.lastname@example.org> Cc: git <email@example.com>, Johannes Schindelin <firstname.lastname@example.org> Subject: Re: [GSOC] Introduction Date: Thu, 23 Jan 2020 23:38:11 +0100 [thread overview] Message-ID: <CAP8UFD3ywtc0Xo8nu22-Uyu78-ehXQxBnHD3eXhc1yvfkqbNdg@mail.gmail.com> (raw) In-Reply-To: <CA+CkUQ8vDG6HHyzX=bEEmzsZX0uCm4cpRD5zev5tY18ZFueuPw@mail.gmail.com> Hi Hariom, On Thu, Jan 23, 2020 at 9:18 PM Hariom verma <email@example.com> wrote: > > On Thu, Jan 23, 2020 at 4:46 PM Christian Couder > <firstname.lastname@example.org> wrote: > > > > It is not clear looking only at the links if the issues you solved > > have resulted in some patches posted to the Git mailing list or just > > fixes in Git for Windows. Could you give us more details about that? > > For example if you sent emails to the mailing list could you send > > links to those emails? > > My apologies, here are the links to the patches. Great, thanks! > > If you have already sent patches to the mailing list and they have > > been accepted, you don't need to work on a microproject. > > Both have been accepted and merged successfully. Those are just minor > issues, so I don't they can be qualify as microproject. Although I > forgot to tag [GSoC] with the patches. I think it is enough for a microproject. > Few Doubts: > 1. Do I need to tag [GSoC] with every patch I will send before GSoC or > just only with a microproject? I think it's better, except when replying, if you tag every email you send before the end of the GSoC with [GSoC]. > 2. Can I use GitGitGadget throughout the GSoC period and for my > microproject? (I'm quite liking this tool) I think so. I think other GSoC students and Outreachy interns have done. Best, Christian.
next prev parent reply other threads:[~2020-01-23 22:38 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-01 13:02 Hariom verma 2020-01-23 11:16 ` Christian Couder 2020-01-23 20:18 ` Hariom verma 2020-01-23 22:38 ` Christian Couder [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-01-22 20:42 [GSoC] Introduction Shourya Shukla 2020-01-23 11:02 ` Christian Couder 2020-01-23 18:04 ` Shourya Shukla 2020-01-23 22:51 ` Christian Couder 2019-02-24 10:05 Rohit Ashiwal 2019-02-24 14:47 ` Johannes Schindelin 2019-02-25 6:50 ` Christian Couder 2019-02-25 11:35 ` Rohit Ashiwal 2019-02-25 20:21 ` Christian Couder 2019-02-25 21:09 ` Eric Sunshine 2015-03-07 11:25 [GSOC] Introduction karthik nayak
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=CAP8UFD3ywtc0Xo8nu22-Uyu78-ehXQxBnHD3eXhc1yvfkqbNdg@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [GSOC] Introduction' \ /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).