From: kerylefondji7@gmail.com
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, christiancouder@gmail.com,
siddharthasthana31@gmail.com
Subject: Re: [Outreachy][PATCH v2] builtin/var: refactor to use parse-options API
Date: Sat, 17 Oct 2026 13:20:44 +0100 [thread overview]
Message-ID: <20261017122044.568-1-kerylefondji7@gmail.com> (raw)
In-Reply-To: <1a146af667a8bcd4>
Hi Kristoffer,
Thank you very much for your feedback and pointing this out. I will fix this immediately with my correct email address for the next version.
Best regards,
Keryle
prev parent reply other threads:[~2026-10-17 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a146af667a8bcd4>
2026-10-17 0:54 ` [Outreachy][PATCH v2] builtin/var: refactor to use parse-options API Keryle
2026-10-17 11:25 ` kerylefondji7
2026-10-17 11:45 ` Kristoffer Haugsbakk
2026-10-17 12:20 ` kerylefondji7 [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=20261017122044.568-1-kerylefondji7@gmail.com \
--to=kerylefondji7@gmail.com \
--cc=christiancouder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=siddharthasthana31@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