From: Britton Kerin <britton.kerin@gmail.com>
To: git@vger.kernel.org
Subject: git-send-email doesn't entirely understand --subject (or --in-reply-to)
Date: Mon, 18 Jul 2022 15:40:59 -0800 [thread overview]
Message-ID: <CAC4O8c-Tf11CpwuRudyrpXv5bGshuyEenV9kKrs0zRWER-+yHA@mail.gmail.com> (raw)
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 reply other threads:[~2022-07-18 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 23:40 Britton Kerin [this message]
2022-07-22 20:18 ` git-send-email doesn't entirely understand --subject (or --in-reply-to) Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC4O8c-Tf11CpwuRudyrpXv5bGshuyEenV9kKrs0zRWER-+yHA@mail.gmail.com \
--to=britton.kerin@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).