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

git-send-email doesn't entirely understand --subject (or --in-reply-to)

From
Britton Kerin <britton.kerin@gmail.com>
Date
Jul 18, 2022, 23:40 UTC
Message-ID
<CAC4O8c-Tf11CpwuRudyrpXv5bGshuyEenV9kKrs0zRWER-+yHA@mail.gmail.com>

I'm not absolutely sure this is git's fault but I tried to use the reply mechanism described here:

     https://public-inbox.org/git/20220718232843.151392-1-britton.kerin@gmail.com/#R
whic is to say this:
     git send-email \
         --in-reply-to=20220718232843.151392-1-britton.kerin@gmail.com \
         --to=britton.kerin@gmail.com \
         --cc=git@vger.kernel.org \
         --cc=gitster@pobox.com \
         --cc=newren@gmail.com \
         --subject='Re: BUG: git-check-ignore documentation doesn'\''t
come close to describing what it really does' \
         /path/to/YOUR_REPLY
and it failed like this:

$ git send-email --in-reply-to=xmqqtu7lc587.fsf@gitster.g --to=britton.kerin@gmail.com --subject='Re: BUG: git-check-ignore documentation doesn'\''t come close to describing what it really does' ~/my_reply_git_checkignore_bug_post /home/bkerin/my_reply_git_checkignore_bug_post No subject line in /home/bkerin/my_reply_git_checkignore_bug_post? at /usr/lib/git-core/git-send-email line 720.

Until I added this line to the top of /home/bkerin/my_reply_git_checkignore_bug_post:

     Subject: Re: BUG: git-check-ignore documentation doesn't come
close to describing what it really does

maybe this is normal but it seems weird given the presence of --in-reply-to and --subject and the fact that I didn't need to copy any other headers in.

Britton
Next: Eric Wong
Message 1 of 2 in “git-send-email doesn't entirely understand --subject (or --in-reply-to)”
  1. Britton KerinJul 18, 2022
  2. Eric WongJul 22, 2022

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.