From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Derrick Stolee <stolee@gmail.com>,
Ananya Krishna Maram <ananyakittu1997@gmail.com>,
christian.couder@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH][Outreachy] remove all the inclusions of git-compat-util.h in header files
Date: Wed, 10 Oct 2018 17:46:38 +0900 [thread overview]
Message-ID: <xmqq4ldumbo1.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1810100856570.2034@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 10 Oct 2018 10:06:50 +0200 (DST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Personally, I find the "whoever is picking it up should do the thinking"
> much too harsh for a first-time contributor who specifically came through
> the Outreachy program, i.e. expected to have a gentle introduction into
> the project, and into the ways we work.
Oh, absolutely I agree.
Any random discussion participant can say "left over bits" in any
random message with an idea that is left on the table. Looking for
it may narrow the set messages to be examined, but the query result
will inevitably be still full of chaff. It is not a very good match
for "gentle introduction" material for GSoC/Outreachy microprojects.
List of reasonable low-hanging fruits is hard to maintain, as the
cost of building and maintaining such a list would easily outweigh
the cost (and fun) of picking these low-hanging fruits yourself X-<.
I do not think of a good solution to help newcomers offhand.
Thanks, as always, for trying to be helpful to newcomers.
next prev parent reply other threads:[~2018-10-10 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 17:05 [PATCH][Outreachy] remove all the inclusions of git-compat-util.h in header files Ananya Krishna Maram
2018-10-08 17:13 ` Derrick Stolee
2018-10-09 2:16 ` Ananya Krishna Maram
2018-10-09 10:13 ` Junio C Hamano
2018-10-10 8:06 ` Johannes Schindelin
2018-10-10 8:46 ` Junio C Hamano [this message]
2018-10-10 9:13 ` Christian Couder
2018-10-10 12:22 ` 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=xmqq4ldumbo1.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ananyakittu1997@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=stolee@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.
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).