From: Caleb Tillman <caleb.tillman@gmail.com>
To: git@vger.kernel.org
Subject: [New, Outreachy] Introduction
Date: Fri, 16 Oct 2020 13:15:53 -0500 [thread overview]
Message-ID: <CAES5DXRFu7yaM3TggA7p9Yot-E2O1SmpmT+B6ddZmHgRmCmuNw@mail.gmail.com> (raw)
Hi,
I am an Outreachy applicant interested in open source development. I
have started reading through docs for this project, and noticed that
many of the tests in t/ that are marked as expected to succeed are
failing. Is this normal and to be expected, or is there I chance I
messed something up in the build phase.
Also, for my microproject I was considering replacing some of the
calls to 'test' in t/ with their debug-friendly helper functions.
There seem to still be a lot of files that would qualify. Is this
particular microproject still desired?
Thanks ahead of time for your help.
Caleb Tillman
next reply other threads:[~2020-10-16 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 18:15 Caleb Tillman [this message]
2020-10-16 18:31 ` [New, Outreachy] Introduction Emily Shaffer
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=CAES5DXRFu7yaM3TggA7p9Yot-E2O1SmpmT+B6ddZmHgRmCmuNw@mail.gmail.com \
--to=caleb.tillman@gmail.com \
--cc=git@vger.kernel.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).