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

Re: [PATCH] Provide better feedback for the untracked only case in status output

From
JRJuergen Ruehle <j.ruehle@bmiag.de>
Date
Jan 10, 2007, 18:33 UTC
Message-ID
<17829.12657.814000.514351@lapjr.intranet.kiel.bmiag.de>
In-Reply-To
<7v4pqzfhzd.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano writes:
 > Juergen Ruehle <j.ruehle@bmiag.de> writes:
 > 
 > > Juergen Ruehle writes:
 > >  > [Corrupted patch deleted]
 > >
 > > Will try again when I know what happened.
 > 
 > While you are at it, let me point out one thing that has been
 > annoying me for a while.
 > 
 >  * The message claims to be from git-send-email;
 > 
 >  * Content-Type and CTE are UTF-8 and QP (which is fine);
 > 
 >  * You have in-body From: line; this is not wrong per-se and I
 >    understand why you would want one (your e-mail From: line
 >    uses ASCII approximations "ue" and "ue" and you would want
 >    the resulting commit to spell your name correctly).
 >
 >  * However, this in-body From: line is _doubly_ QP encoded (what
 >    you see above is your name, first RFC 2047 encoded and then
 >    QP encoded).  It shouldn't be.
 > 
 > So, my questions are:
 > 
 >  (1) is this what git-send-email generates and sends out by
 >      default?  If so that means it is a bug in that program that
 >      needs to be fixed.
 > 
 >  (2) if not, are you inserting the in-body From: by hand,
 >      perhaps cut & paste from format-patch output, before
 >      feeding git-send-email (which runs QP on it)?
 > 
 > If the latter, please do not paste the RFC 2047 quoted form.
 > You can spell your name in raw UTF-8 on the in-body From: line
 > just like you did on your Signed-off-by: line.

Yes, this is using git-send-email which sends the mail as 8bit encoded and provides the QP encoded From line. Unfortunately there seems to be a gateway in between that doesn't handle 8bit and QPs the mail again. Perhaps I need some other switches for format-patch and send-email to produce a better result? I'll take another look at the documentation before annoying you again.

Previous: Junio C HamanoNext: Juergen Ruehle
Message 15 of 26 in “Suggest use of "git add file1 file2" when there is nothing to commit.”
  1. 1/2 Suggest use of "git add file1 file2" when there is nothing to commit.Shawn O. Pearce, Dec 16, 2006
  2. Michael LoefflerJan 5, 2007
  3. Junio C HamanoJan 5, 2007
  4. Junio C HamanoJan 6, 2007
  5. Juergen RuehleJan 6, 2007
  6. Junio C HamanoJan 6, 2007
  7. Juergen RuehleJan 6, 2007
  8. Junio C HamanoJan 8, 2007
  9. Juergen RuehleJan 8, 2007
  10. Junio C HamanoJan 8, 2007
  11. Provide better feedback for the untracked only case in status outputJuergen Ruehle, Jan 10, 2007
  12. Juergen RuehleJan 10, 2007
  13. Juergen RuehleJan 10, 2007
  14. Junio C HamanoJan 10, 2007
  15. Juergen RuehleJan 10, 2007
  16. Quick hack to avoid double qp encodingJuergen Ruehle, Jan 10, 2007
  17. Juergen RuehleJan 10, 2007
  18. Junio C HamanoJan 10, 2007
  19. Michael LoefflerJan 10, 2007
  20. Juergen RuehleJan 10, 2007
  21. Provide better feedback for the untracked only case in status outputJuergen Ruehle, Jan 10, 2007
  22. Jeff KingJan 10, 2007
  23. Juergen RuehleJan 11, 2007
  24. Juergen RuehleJan 6, 2007
  25. Michael LoefflerJan 8, 2007
  26. Juergen RuehleJan 9, 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.