git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
	Eric Sunshine <sunshine@sunshineco.com>
Subject: [PATCH 2/1] mailinfo: don't insert header prefix for handle_content_type()
Date: Mon, 10 Feb 2020 08:15:19 +0100	[thread overview]
Message-ID: <35ef5149-2da9-a147-fb5b-8f175ff617e7@web.de> (raw)
In-Reply-To: <b31c46a8-380b-3528-27a5-a2dddacaf837@web.de>

handle_content_type() only cares about the value after "Content-Type: ";
there is no need to insert that string for it.

Suggested-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: René Scharfe <l.s.r@web.de>
---
 mailinfo.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/mailinfo.c b/mailinfo.c
index 543962d40c..402ef04dd1 100644
--- a/mailinfo.c
+++ b/mailinfo.c
@@ -570,7 +570,6 @@ static int check_header(struct mailinfo *mi,
 		len = strlen("Content-Type: ");
 		strbuf_add(&sb, line->buf + len, line->len - len);
 		decode_header(mi, &sb);
-		strbuf_insertstr(&sb, 0, "Content-Type: ");
 		handle_content_type(mi, &sb);
 		ret = 1;
 		goto check_header_out;
--
2.25.0

  parent reply	other threads:[~2020-02-10  7:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08 19:56 [PATCH] strbuf: add and use strbuf_insertstr() René Scharfe
2020-02-08 23:08 ` Taylor Blau
2020-02-09 10:23   ` René Scharfe
2020-02-09  0:53 ` Eric Sunshine
2020-02-09 10:23   ` René Scharfe
2020-02-09 13:44 ` [PATCH v2] " René Scharfe
2020-02-09 17:36   ` Eric Sunshine
2020-02-09 18:28     ` René Scharfe
2020-02-09 21:09       ` Eric Sunshine
2020-02-09 23:10       ` Taylor Blau
2020-02-10 23:44     ` Jeff King
2020-02-11 16:17       ` Junio C Hamano
2020-02-11 17:16         ` [PATCH 0/4] some more mailinfo cleanups Jeff King
2020-02-11 17:18           ` [PATCH 1/4] mailinfo: treat header values as C strings Jeff King
2020-02-11 17:26             ` Eric Sunshine
2020-02-11 17:19           ` [PATCH 2/4] mailinfo: simplify parsing of header values Jeff King
2020-02-11 17:19           ` [PATCH 3/4] mailinfo: be more liberal with header whitespace Jeff King
2020-02-11 17:20           ` [PATCH 4/4] mailinfo: factor out some repeated header handling Jeff King
2020-02-11 16:18       ` [PATCH v2] strbuf: add and use strbuf_insertstr() René Scharfe
2020-02-11 17:13         ` Jeff King
2020-02-10  7:15   ` René Scharfe [this message]
2020-02-10 17:27     ` [PATCH 2/1] mailinfo: don't insert header prefix for handle_content_type() Junio C Hamano
2020-02-10 19:55     ` Taylor Blau

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35ef5149-2da9-a147-fb5b-8f175ff617e7@web.de \
    --to=l.s.r@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).