git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] strbuf: add and use strbuf_insertstr()

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Feb 9, 2020, 21:09 UTC
Message-ID
<CAPig+cQCwxopnwC+VYgS39QpaSW10JWW4HZGYzeq+psvB1bLMA@mail.gmail.com>
In-Reply-To
<60b491a1-2b71-d5a5-398f-e6743e2c617a@web.de>
On Sun, Feb 9, 2020 at 1:28 PM René Scharfe <l.s.r@web.de> wrote:
Show 6 quoted lines
> Am 09.02.20 um 18:36 schrieb Eric Sunshine:
> > Digging deeper, though, I have to wonder why this bothers inserting
> > "Content-Type: " at all. [...]
>
> Do you care to send a follow-up patch (or one against master if you're
> not convinced by my reasoning given above)?

It's unlikely I will get to it any time soon. I'm still sitting on unfinished patches I started 1.5 years ago and have a queue of "git worktree"-related tasks on my To-Do list.

Previous: René ScharfeNext: Taylor Blau
Message 9 of 23 in “strbuf: add and use strbuf_insertstr()”
  1. strbuf: add and use strbuf_insertstr()René Scharfe, Feb 8, 2020
  2. Taylor BlauFeb 8, 2020
  3. René ScharfeFeb 9, 2020
  4. Eric SunshineFeb 9, 2020
  5. René ScharfeFeb 9, 2020
  6. strbuf: add and use strbuf_insertstr()René Scharfe, Feb 9, 2020
  7. Eric SunshineFeb 9, 2020
  8. René ScharfeFeb 9, 2020
  9. Eric SunshineFeb 9, 2020
  10. Taylor BlauFeb 9, 2020
  11. Jeff KingFeb 10, 2020
  12. Junio C HamanoFeb 11, 2020
  13. 0/4 some more mailinfo cleanupsJeff King, Feb 11, 2020
  14. 1/4 mailinfo: treat header values as C stringsJeff King, Feb 11, 2020
  15. Eric SunshineFeb 11, 2020
  16. 2/4 mailinfo: simplify parsing of header valuesJeff King, Feb 11, 2020
  17. 3/4 mailinfo: be more liberal with header whitespaceJeff King, Feb 11, 2020
  18. 4/4 mailinfo: factor out some repeated header handlingJeff King, Feb 11, 2020
  19. René ScharfeFeb 11, 2020
  20. Jeff KingFeb 11, 2020
  21. 2/1 mailinfo: don't insert header prefix for handle_content_type()René Scharfe, Feb 10, 2020
  22. Junio C HamanoFeb 10, 2020
  23. Taylor BlauFeb 10, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.