Github messages for mblaze
 help / color / mirror / Atom feed
From: rheoli <rheoli@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Use tolower instead of lc
Date: Thu, 16 Mar 2023 17:52:34 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-235@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

There is a new pull request by rheoli against master on the mblaze repository

https://github.com/rheoli/mblaze master
https://github.com/leahneukirchen/mblaze/pull/235

Use tolower instead of lc
Use tolower instead of lc as there are some M365 header with _ in the name of headers (example msip_label).

A patch file from https://github.com/leahneukirchen/mblaze/pull/235.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-235.patch --]
[-- Type: text/x-diff, Size: 821 bytes --]

From 417847fd89af92fb8c2a6908df264bcd8db485f6 Mon Sep 17 00:00:00 2001
From: Stephan Toggweiler <609601+rheoli@users.noreply.github.com>
Date: Thu, 16 Mar 2023 17:36:05 +0100
Subject: [PATCH] use tolower instead of lc as there are some M365 header with
 _ in the name of headers

---
 blaze822.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/blaze822.c b/blaze822.c
index 47f03a2..b960b0b 100644
--- a/blaze822.c
+++ b/blaze822.c
@@ -396,7 +396,7 @@ unfold_hdr(char *buf, char *end)
 	s = buf;
 
 	while (s < end && *s != ':' && *s != '\n') {
-		*s = lc(*s);
+		*s = tolower(*s);
 		s++;
 	}
 
@@ -412,7 +412,7 @@ unfold_hdr(char *buf, char *end)
 			compress_hdr(l, s-1);
 			l = s;
 			while (s < end && *s != ':' && *s != '\n') {
-				*s = lc(*s);
+				*s = tolower(*s);
 				s++;
 			}
 		}

             reply	other threads:[~2023-03-16 16:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 16:52 rheoli [this message]
2023-03-16 18:33 ` leahneukirchen
2023-03-16 18:56 ` [PR PATCH] [Closed]: " leahneukirchen

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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-235@inbox.vuxu.org \
    --to=rheoli@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).