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

Re: FEATURE REQUEST: git-format-path: Add option to encode patch content

From
Junio C Hamano <junkio@cox.net>
Date
Apr 28, 2007, 00:56 UTC
Message-ID
<7vps5pl3jl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87y7kdo6pn.wl%cworth@cworth.org>
Carl Worth <cworth@cworth.org> writes:
Show 11 quoted lines
>> In the community git originates from, even --inline attachments
>> are frowned upon, let alone --attach multiparts (yes, I am
>> talking about the kernel list and this list).  Nobody who sends
>> patches over e-mail in communities that have a tradition against
>> unreadable patches would be using --inline nor --attach anyway,
>> so making --attach to do base64 would not hurt there.
>
> I know I'm not within the kernel or git party line by saying this, but
> I don't have a problem with (non base64) mime-attached patches. My MUA
> displays them fine and quotes them when I reply so I can easily review
> them.

You strayed into tangent here. You said you do not have a problem with non base64 attachments. I would like to know if you have or do not have problem with base64 ones, as that is what indicates your opinion on making --attach unconditionally do base64 which was the suggestion made in the thread.

Previous: Carl WorthNext: Carl Worth
Message 18 of 20 in “FEATURE REQUEST: git-format-path: Add option to encode patch content”
  1. Jari AaltoApr 27, 2007
  2. Johannes SchindelinApr 27, 2007
  3. Jari AaltoApr 27, 2007
  4. Alex RiesenApr 27, 2007
  5. Johannes SchindelinApr 28, 2007
  6. Junio C HamanoApr 27, 2007
  7. Robin H. JohnsonApr 27, 2007
  8. Carl WorthApr 27, 2007
  9. Junio C HamanoApr 27, 2007
  10. Linus TorvaldsApr 27, 2007
  11. Carl WorthApr 27, 2007
  12. Linus TorvaldsApr 27, 2007
  13. Linus TorvaldsApr 27, 2007
  14. Carl WorthApr 27, 2007
  15. Linus TorvaldsApr 28, 2007
  16. Junio C HamanoApr 28, 2007
  17. Carl WorthApr 30, 2007
  18. Junio C HamanoApr 28, 2007
  19. Carl WorthApr 30, 2007
  20. Junio C HamanoApr 30, 2007

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.