git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: christian.couder@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com,
	johannes.schindelin@gmx.de,
	Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: Re: [GSoC] Introduction
Date: Thu, 23 Jan 2020 23:34:21 +0530
Message-ID: <20200123180421.16720-1-shouryashukla.oo@gmail.com> (raw)
In-Reply-To: <CAP8UFD2Fo=2suQDLwzLM-Wg3ZzXpqHw-x0brPtPV0d4dRsgs9A@mail.gmail.com>

Hey Christian,

Thank you for your advice! Apologies for not tagging my patch with [GSoC],
I didn't realise it before. Is it okay if I try solving a couple of issues
and then focus on the GSoC project(following from what you advised)? 

Also, I wanted to ask whether or not one can try attempting the projects mentioned
last year[1] this year as well? I observed that only one idea[2] was picked out of
the aforementioned project list.

Merci,
Shourya

[1]: https://git.github.io/SoC-2019-Ideas/
[2]: https://summerofcode.withgoogle.com/archive/2019/projects/5390155215536128/


  reply	other threads:[~2020-01-23 18:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 20:42 Shourya Shukla
2020-01-23 11:02 ` Christian Couder
2020-01-23 18:04   ` Shourya Shukla [this message]
2020-01-23 22:51     ` Christian Couder
  -- strict thread matches above, loose matches on Subject: below --
2020-01-01 13:02 [GSOC] Introduction Hariom verma
2020-01-23 11:16 ` Christian Couder
2020-01-23 20:18   ` Hariom verma
2020-01-23 22:38     ` Christian Couder
2019-02-24 10:05 [GSoC] Introduction 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=20200123180421.16720-1-shouryashukla.oo@gmail.com \
    --to=shouryashukla.oo@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git