Re: [GSOC] Introduction

From: Christian Couder <christian.couder@gmail.com>
Date: Jan 23, 2020, 22:38 UTC
Message-ID: <CAP8UFD3ywtc0Xo8nu22-Uyu78-ehXQxBnHD3eXhc1yvfkqbNdg@mail.gmail.com>
In-Reply-To: <CA+CkUQ8vDG6HHyzX=bEEmzsZX0uCm4cpRD5zev5tY18ZFueuPw@mail.gmail.com>

Hi Hariom,

On Thu, Jan 23, 2020 at 9:18 PM Hariom verma <hariom18599@gmail.com> wrote:

Show 11 quoted lines

>
> On Thu, Jan 23, 2020 at 4:46 PM Christian Couder
> <christian.couder@gmail.com> 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[1][2].

Great, thanks!

Show 6 quoted lines

> > 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.