From: Christian Couder <christian.couder@gmail.com>
To: trickygitninja@gmail.com
Cc: git <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: How to start contributing
Date: Sat, 20 Oct 2018 08:47:35 +0200 [thread overview]
Message-ID: <CAP8UFD3CDwu7OVgVmEgP2Se_bxYszcze68_bXT7=wgZaxncpzg@mail.gmail.com> (raw)
In-Reply-To: <CAJKt3eP+BZkfK_yn3KYWMgmJB8_18UFr5eizmdGOY_4vM5=AYA@mail.gmail.com>
Hi,
On Thu, Oct 18, 2018 at 2:51 PM Πλάτων Κιορπελίδης
<trickygitninja@gmail.com> wrote:
>
> Hello,
>
> I’m a computer science student and I’m interested in contributing to git.
> I’ve read the GSoC git page with the ideas and micro-projects as I’m
> interested in participating next summer.
> I’ve also read the Documentation at the GitHub mirror.
> I’ve never worked on such large project and I don’t know where to start from.
> I’ve picked this microproject from the GSoC page:
>
> Make “git tag –contains <id>” less chatty if <id> is invalid
> “git tag – contains <id>” prints the whole help text if <id> is
> invalid. It should only show the error message instead.
> Thread: https://public-inbox.org/git/20160118215433.GB24136@sigill.intra.peff.net/
>
> This bug is solved using the 3rd option, but I suspect that it’s still
> here because the 2nd option is preferred.
I think it should probably have been removed from the micro-project
list. I am CC'ing Peff as he wrote the email listing the different
options to solve the original issue and may think otherwise.
> How should I tackle this?
It's a good first step to ask first on the list as you did if it is a
good micro-project or not. Unfortunately in this case I think you
might want to try to find another micro-project.
Thanks,
Christian.
next prev parent reply other threads:[~2018-10-20 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 12:49 How to start contributing Πλάτων Κιορπελίδης
2018-10-20 6:47 ` Christian Couder [this message]
2018-10-24 8:19 ` Jeff King
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='CAP8UFD3CDwu7OVgVmEgP2Se_bxYszcze68_bXT7=wgZaxncpzg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=trickygitninja@gmail.com \
/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.
Code repositories for project(s) associated with this public 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).