# [GSOC] Introduction 4 messages from 2020-01-01 to 2020-01-23. Participants: Hariom verma, Christian Couder. Thread: https://gitlist.dev/t/52547 ## Hariom verma, 2020-01-01 13:02 Subject: [GSOC] Introduction Message-ID: URL: https://gitlist.dev/e/CA%2BCkUQ-72jKTMUQuGvYg%2Bo5bp3DoKxX5bFCUrWyGLf_tzVydsw%40mail.gmail.com ``` Hello, I'm Hariom Verma, a third-year Computer Science Engineering Student. I'm using Git for almost 2 years and want to contribute to the same. I had gone through the solid part of 'SubmittingPatches' and 'Historical Summer of Code Materials'. I previously solved 2 issues[1][2] with the help of dscho and looking forward to work on more before working on minor project to have a good understanding of Git's Code. But thought I'd take a quick break to introduce myself. Thanks Hariom Verma [1]: https://github.com/gitgitgadget/git/issues/357 [2]: https://github.com/gitgitgadget/git/issues/399 ``` ## Christian Couder, 2020-01-23 11:16 Subject: Re: [GSOC] Introduction Message-ID: URL: https://gitlist.dev/e/CAP8UFD20Jh4HRBUTUfy6t72r_wyX3F2RWoyRVwBx4dY2VfhrbA%40mail.gmail.com In-Reply-To: ``` Hi, On Wed, Jan 1, 2020 at 2:05 PM Hariom verma wrote: > > Hello, > I'm Hariom Verma, a third-year Computer Science Engineering Student. > I'm using Git for almost 2 years and want to contribute to the same. I had > gone through the solid part of 'SubmittingPatches' and 'Historical Summer of > Code Materials'. Thank you for getting in touch with us! Also sorry for the late answer. I think many people had a vacation around January 1st and I think that's why your email fell through the cracks. > I previously solved 2 issues[1][2] with the help of dscho and looking > forward to work on more before working on minor project to have a good > understanding of Git's Code. But thought I'd take a quick break to > introduce myself. 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? If you have already sent patches to the mailing list and they have been accepted, you don't need to work on a microproject and I would then suggest to look at the following: https://public-inbox.org/git/CAP8UFD2Fo=2suQDLwzLM-Wg3ZzXpqHw-x0brPtPV0d4dRsgs9A@mail.gmail.com/ Best, Christian. ``` ## Hariom verma, 2020-01-23 20:18 Subject: Re: [GSOC] Introduction Message-ID: URL: https://gitlist.dev/e/CA%2BCkUQ8vDG6HHyzX%3DbEEmzsZX0uCm4cpRD5zev5tY18ZFueuPw%40mail.gmail.com In-Reply-To: ``` Hi Christian, On Thu, Jan 23, 2020 at 4:46 PM Christian Couder 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]. > 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. Few Doubts: 1. Do I need to tag [GSoC] with every patch I will send before GSoC or just only with a microproject? 2. Can I use GitGitGadget throughout the GSoC period and for my microproject? (I'm quite liking this tool) Regards, Hariom [1]: https://public-inbox.org/git/3b4b8e0353d705ea649c9fb608c021b35e6d8f5b.1571250635.git.gitgitgadget@gmail.com/ [2]: https://public-inbox.org/git/177deddcf83c2550c0db536a7a6942ba69a92fa5.1574600963.git.gitgitgadget@gmail.com/ ``` ## Christian Couder, 2020-01-23 22:38 Subject: Re: [GSOC] Introduction Message-ID: URL: https://gitlist.dev/e/CAP8UFD3ywtc0Xo8nu22-Uyu78-ehXQxBnHD3eXhc1yvfkqbNdg%40mail.gmail.com In-Reply-To: ``` Hi Hariom, On Thu, Jan 23, 2020 at 9:18 PM Hariom verma wrote: > > On Thu, Jan 23, 2020 at 4:46 PM Christian Couder > 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! > > 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. ```