git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Isoken Ibizugbe <isokenjune@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [Outreachy] Introduction and Interest in Contributing to the Git Community
Date: Wed, 11 Oct 2023 10:47:19 +0200	[thread overview]
Message-ID: <CAP8UFD1f2o2mmK1kBug52WE+PXOzhhPCi8y-jELkF2J+VZos5w@mail.gmail.com> (raw)
In-Reply-To: <CAJHH8bFLqs7B5UaCFZv+P8yS2zeXLoKoV6YTUB_xFcG8ZLn_WA@mail.gmail.com>

Hi Isoken,

On Wed, Oct 11, 2023 at 7:48 AM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Hi Christian,
>
> I hope you're doing well. I did some research,

Nice that you did some research and are mentioning it.

However please reply inline instead of top-posting (see
https://en.wikipedia.org/wiki/Posting_style). On
https://git.github.io/General-Microproject-Information/ there is a
section called "Some conventions and tips" which has a "Reply inline"
subsection about this.

> but unfortunately, I
> couldn't find any clear documentation stating that setup tests should
> be renamed.

Ok, so it's indeed better to find something else to work on.

> However, I did find another issue that I think I could
> work on - 'Amend error messages and prompts of various (sub)commands
> #635'. Should I go on with it?

Yeah, I think it's a good idea to work on this. See this discussion
thread where we give advice to Naomi about improving error messages as
microproject:

https://lore.kernel.org/git/CACS=G2zsJxP+NWuosZyrFGctJptHNYTrULErRo_Ns41KeMuMqA@mail.gmail.com/#r

Thanks,
Christian.

  reply	other threads:[~2023-10-11  8:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 10:19 [Outreachy] Introduction and Interest in Contributing to the Git Community Isoken Ibizugbe
2023-10-04 10:20 ` Christian Couder
2023-10-07 10:25   ` Isoken Ibizugbe
2023-10-08 10:50     ` Christian Couder
2023-10-09 13:31       ` Isoken Ibizugbe
2023-10-09 13:38         ` Christian Couder
2023-10-11  5:46           ` Isoken Ibizugbe
2023-10-11  8:47             ` Christian Couder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-09 18:31 Doreen Wanyama
2023-10-11  6:06 ` Naomi Ibe
2023-10-11 14:48   ` Doreen Wanyama

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=CAP8UFD1f2o2mmK1kBug52WE+PXOzhhPCi8y-jELkF2J+VZos5w@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=isokenjune@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).