git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Hariom verma <hariom18599@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>, johannes.schindelin@gmx.de
Subject: Re: [GSOC] Introduction
Date: Fri, 24 Jan 2020 01:48:13 +0530	[thread overview]
Message-ID: <CA+CkUQ8vDG6HHyzX=bEEmzsZX0uCm4cpRD5zev5tY18ZFueuPw@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD20Jh4HRBUTUfy6t72r_wyX3F2RWoyRVwBx4dY2VfhrbA@mail.gmail.com>

Hi Christian,

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

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

  reply	other threads:[~2020-01-23 20:18 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 [this message]
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='CA+CkUQ8vDG6HHyzX=bEEmzsZX0uCm4cpRD5zev5tY18ZFueuPw@mail.gmail.com' \
    --to=hariom18599@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --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).