From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Moritz Neeb <lists@moritzneeb.de>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Starting on a microproject for GSoC
Date: Thu, 28 Jan 2016 09:22:40 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1601280919240.2964@virtualbox> (raw)
In-Reply-To: <CAH5451=u1MB=LJyBv+Z9e4Y5ncHktMw+oEycOWV1YXASaawMDA@mail.gmail.com>
Hi Moritz & Andrew,
On Thu, 28 Jan 2016, Andrew Ardill wrote:
> On 28 January 2016 at 11:40, Moritz Neeb <lists@moritzneeb.de> wrote:
> > I suppose just fixing/revising this would be kind
> > of a too low hanging fruit?
>
> I am in no way qualified to speak to the majority of your post, but I
> can't imagine anyone refusing your work because it was 'too low
> hanging fruit'.
I would agree that it is *not* a "too low hanging fruit".
The thing is, it would be a really easy way to get into the groove, to
understand how changes are expected to be contributed, what the process of
iterating the patches/patch series is, and in what form the patches are
preferred.
Moritz, if you worry about this lil' project to be too little, why don't
you just start with it and then tackle another one? That way, you will be
already very familiar with the Git project (and the regulars will be
familiar with you) when GSoC comes around.
Ciao,
Johannes
next prev parent reply other threads:[~2016-01-28 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 0:40 Starting on a microproject for GSoC Moritz Neeb
2016-01-28 1:18 ` Stefan Beller
2016-01-28 10:37 ` Moritz Neeb
2016-01-28 6:17 ` Andrew Ardill
2016-01-28 8:22 ` Johannes Schindelin [this message]
2016-01-28 8:51 ` Lars Schneider
2016-01-28 19:45 ` Junio C Hamano
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=alpine.DEB.2.20.1601280919240.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=lists@moritzneeb.de \
/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).