From: Olamide Caleb Bello <belkid98@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, gitster@pobox.com,
usmanakinyemi202@gmail.com,
Olamide Caleb Bello <belkid98@gmail.com>
Subject: [PATCH 0/2] [Outreachy] gpg-interface.c: use string_list_split instead of strbuf_split_max
Date: Wed, 15 Oct 2025 02:19:41 +0000 [thread overview]
Message-ID: <cover.1760490943.git.belkid98@gmail.com> (raw)
The array of strbufs that calls to strbuf_split_max provides are merely
used to store the list of tokens gotten from the split and no edit are
done on these resulting splits making the strbuf_split_max unideal
for this usecase.
This patchset replaces these instances with the modern string_list_split
Olamide Caleb Bello (2):
gpg-interface: replace strbuf_split with string_list_split
gpg-interface: use string_list_split instead of strbuf_split
gpg-interface.c | 24 ++++++++++--------------
1 file changed, 10 insertions(+), 14 deletions(-)
--
2.51.0.463.g79cf913ea9
next reply other threads:[~2025-10-15 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:19 Olamide Caleb Bello [this message]
2025-10-15 2:19 ` [PATCH 1/2] [Outreachy] gpg-interface: replace strbuf_split with string_list_split Olamide Caleb Bello
2025-10-15 15:01 ` Christian Couder
2025-10-15 21:56 ` Bello Olamide
2025-10-15 2:19 ` [PATCH 2/2] [Outreachy] gpg-interface: use string_list_split instead of strbuf_split Olamide Caleb Bello
2025-10-15 15:28 ` Christian Couder
2025-10-15 22:02 ` Bello Olamide
2025-10-15 15:40 ` [PATCH 0/2] [Outreachy] gpg-interface.c: use string_list_split instead of strbuf_split_max Christian Couder
2025-10-15 22:05 ` Bello Olamide
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=cover.1760490943.git.belkid98@gmail.com \
--to=belkid98@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).