From: Christian Couder <firstname.lastname@example.org> To: Hariom verma <email@example.com> Cc: git <firstname.lastname@example.org> Subject: Re: [GSOC] Introduction Date: Thu, 23 Jan 2020 12:16:24 +0100 [thread overview] Message-ID: <CAP8UFD20Jh4HRBUTUfy6t72r_wyX3F2RWoyRVwBx4dY2VfhrbA@mail.gmail.com> (raw) In-Reply-To: <CA+CkUQ-72jKTMUQuGvYg+o5bp3DoKxX5bFCUrWyGLf_tzVydsw@mail.gmail.com> Hi, On Wed, Jan 1, 2020 at 2:05 PM Hariom verma <email@example.com> 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 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.
next prev parent reply other threads:[~2020-01-23 11:16 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 [this message] 2020-01-23 20:18 ` Hariom verma 2020-01-23 22:38 ` Christian Couder -- 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=CAP8UFD20Jh4HRBUTUfy6t72r_wyX3F2RWoyRVwBx4dY2VfhrbA@mail.gmail.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).