From: kerylefondji7@gmail.com
To: Muritala Mudi <usmanakinyemi202@gmail.com>
Cc: git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Siddharth Asthana <siddharthasthana31@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [Outreachy] Microproject: use Q_() in builtin/checkout.c
Date: Wed, 21 Oct 2026 10:04:08 +0100 [thread overview]
Message-ID: <20261021090408.835-1-kerylefondji7@gmail.com> (raw)
In-Reply-To: <CAO=0-S64w=n47n6yfYoKJie2aFi+T88Sp_qPmFe2RW0xWEwcdQ@mail.gmail.com>
Hi Mudi,
Welcome to the Git community!
It's great that you are taking the time to ask these questions on
the list first before preparing your patch. As a fellow newcomer
working on a microproject, I found that discussing things before
coding saves a lot of time!
Regarding your questions based on what I've learned so far:
About Q_(): Yes, converting to Q_() is good practice for
internationalization. Even if the English text seems to focus on
plural, other languages have different plural rules, so using Q_()
gives translators the right structure.
About keeping the scope small: As a beginner, keeping the patch
simple and limited (like starting with builtin/checkout.c) makes it
much easier to review and test without getting mixed up in multiple
files at once.
Also, Junio C. Hamano recently shared an update about how we should
approach review discussions before sending new versions (v2, etc.)
in MyFirstContribution. You might find it very useful for your workflow:
https://lore.kernel.org/git/xmqqa4o94e0r.fsf@gitster.g/
Good luck with your contribution!
Best regards,
Keryle
next prev parent reply other threads:[~2026-10-21 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 4:18 [Outreachy] Microproject: use Q_() in builtin/checkout.c Muritala Mudi
2026-10-21 9:04 ` kerylefondji7 [this message]
2026-10-21 11:06 ` Tuomas Ahola
2026-10-21 20:32 ` Tanga Joris
2026-10-22 3:44 ` Muritala Mudi
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=20261021090408.835-1-kerylefondji7@gmail.com \
--to=kerylefondji7@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=siddharthasthana31@gmail.com \
--cc=usmanakinyemi202@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