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

Re: [PATCH 2/2] t9803: update commit messages and description

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 21, 2024, 23:25 UTC
Message-ID
<xmqqsf0j5frm.fsf@gitster.g>
In-Reply-To
<CAN7Jk_3A5c=5E+CNyncaT9qe_d85_p6ZHNzJPd0E5ZSjG1kQng@mail.gmail.com>
Sanchit Jindal <sanchit1053@gmail.com> writes:
> I have created another patch with a more descriptive commit message,
> and after squashing it with the earlier commit. I hope it is satisfactory

Hopefully. What GGG sent with v2 label still was a 2-patch series, whose [2/2] patch was an empty patch, though.

> I wanted to ask, Is it possible to send the patches created using
> `git format-patch` manually using gmail, Or the default headers
> applied by `send-email` required.

I do not know where you are using gmail from (I know that Android version has no way to send text-only e-mail for example), but when cutting and pasting the output from format-patch, you should make sure

 * Remove "From <commit object name> Mon Sep 17 00:00:00 2001"
   marker line that signals the beginning of each patch message.  It
   is a mistake to leave this line in the body of your message.
 * Remove "Date: " header.  Do not leave this line in the body of
   your message.
 * Remove "Subject: " header and move its contents to your MUA's
   Subject entry field.
 * Remove "From: " header, and arrange that your MUA puts the same
   "Sanchit Jindal <sanchit1053@gmail.com> on the From header.  If
   your MUA is not cooperating, you can leave that line in the body
   of the message
 * Your cut&paste does not corrupt whitespaces, like squashing two
   consecutive spaces into one, removing the leading whitespaces,
   turning a tab into a run of spaces, folding a line at a
   whitespace in the middle of the message, etc.
 * Your MUA does not turn your text message into HTML gunk.

As long as you do the above carefully, you should be OK. "git format-patch --help" has a section on MUA specific hints, which also might be helpful.

Thanks.
Previous: Sanchit JindalNext: Sanchit Jindal via GitGitGadget
Message 6 of 9 in “t9803-git-p4-shell-metachars.sh: update to use test_path_* functions”
  1. 0/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionsSanchit Jindal via GitGitGadget, Mar 21, 2024
  2. 1/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionssanchit1053 via GitGitGadget, Mar 21, 2024
  3. 2/2 t9803: update commit messages and descriptionSanchit Jindal via GitGitGadget, Mar 21, 2024
  4. Eric SunshineMar 21, 2024
  5. Sanchit JindalMar 21, 2024
  6. Junio C HamanoMar 21, 2024
  7. 0/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionsSanchit Jindal via GitGitGadget, Mar 21, 2024
  8. 1/2 t9803-git-p4-shell-metachars.sh: update to use test_path_* functionssanchit1053 via GitGitGadget, Mar 21, 2024
  9. 2/2 t9803: update commit messages and descriptionSanchit Jindal via GitGitGadget, Mar 21, 2024

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.