From: Christian Couder <christian.couder@gmail.com>
To: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>
Subject: Re: [Outreachy]Amend error messages and prompts of various (sub)commands
Date: Mon, 17 Oct 2022 15:58:47 +0200 [thread overview]
Message-ID: <CAP8UFD1JwZU3DiimZOruLv+x18UFdK5phMxnWnHyiOyh-XR4Ng@mail.gmail.com> (raw)
In-Reply-To: <CA+PPyiEsN9dJj61VdnoT2=TYV54WTLA_-qL4CiT7=imuvuBdmw@mail.gmail.com>
Hi Wilberforce,
On Sat, Oct 15, 2022 at 3:08 PM NSENGIYUMVA WILBERFORCE
<nsengiyumvawilberforce@gmail.com> wrote:
>
> Hi team,
>
> My first microproject is still at seen stage, so I decided to look for
> a good first issue from the repo to get more familiar with the process
> of patch submission and I found I would be interested in
> https://github.com/gitgitgadget/git/issues/635
>
> The Git suite CodingGuidelines suggest this about Error messages, but
> I found that git-compat-util.h contains die("Cannot handle files this
> big"); which breaks one of the rules
>
> I want to change it to die("cannot handle files this big");
>
> Someone should give me a go ahead on this
You can do it if you want, but this would be a very small
contribution. This would be Ok for a microproject, but you have
already worked on one, so you should probably aim at something a bit
more complex. See the "Only ONE quality focused microproject per
applicant" section in
https://git.github.io/General-Microproject-Information/.
By the way, please put your possible mentors (Hariom and me) in Cc.
Thanks,
Christian.
prev parent reply other threads:[~2022-10-17 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 12:22 [Outreachy]Amend error messages and prompts of various (sub)commands NSENGIYUMVA WILBERFORCE
2022-10-17 13:58 ` Christian Couder [this message]
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=CAP8UFD1JwZU3DiimZOruLv+x18UFdK5phMxnWnHyiOyh-XR4Ng@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=nsengiyumvawilberforce@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 read-only IMAP folder(s) and NNTP newsgroup(s).