From: Thomas Gummerer <t.gummerer@gmail.com>
To: Valery Tolstov <me@vtolstov.org>
Cc: git <git@vger.kernel.org>
Subject: Re: GSoC 2017
Date: Sat, 4 Mar 2017 11:45:04 +0000 [thread overview]
Message-ID: <20170304114504.GA27158@hank> (raw)
In-Reply-To: <5334661488625223@web28h.yandex.ru>
Hi,
On 03/04, Valery Tolstov wrote:
> Hi.
>
> Want to participate in GSoC 2017 with Git.
> Can I choose "Make 'git tag --contains <id>' less chatty" as my microproject?
Feel free to choose any microproject from the list. A good way to
start is to check whether other students already attempted the same
microproject before starting with it so you don't duplicate any
work. You can check for that in the mailing list archives, available
at [1].
[1]: https://public-inbox.org/git/
> Thanks.
Good luck!
next prev parent reply other threads:[~2017-03-04 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 11:00 GSoC 2017 Valery Tolstov
2017-03-04 11:45 ` Thomas Gummerer [this message]
2017-03-04 17:26 ` Thomas Gummerer
-- strict thread matches above, loose matches on Subject: below --
2017-03-07 23:22 Valery Tolstov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170304114504.GA27158@hank \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@vtolstov.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).