From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] tolower cleanups
Date: Thu, 22 May 2014 05:43:08 -0400 [thread overview]
Message-ID: <20140522094251.GA14994@sigill.intra.peff.net> (raw)
These two patches were pulled from the http charset series I posted
nearby. The second iteration of that series did not need them, but they
may have value as cleanups.
[1/2]: daemon/config: factor out duplicate xstrdup_tolower
[2/2]: strbuf: add strbuf_tolower function
The first one is a real reduction of code. The second is just making
code public that _might_ get used later, so it's a bit less exciting.
Both are independent of each other, so we can take or leave them
separately.
next reply other threads:[~2014-05-22 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 9:43 Jeff King [this message]
2014-05-22 9:44 ` [PATCH 1/2] daemon/config: factor out duplicate xstrdup_tolower Jeff King
2014-05-22 9:44 ` [PATCH 2/2] strbuf: add strbuf_tolower function Jeff King
[not found] ` <CAP8UFD0PkA_VokFpRkdaKE2UW1AtL6mCY2bOSxOCqX_C9wB=OQ@mail.gmail.com>
2014-05-22 13:42 ` Jeff King
2014-05-22 23:17 ` Kyle J. McKay
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=20140522094251.GA14994@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
/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).