如果使用"--no-thread" 禁用,则不会添加这些标题(除非使用 --in-reply-to 指定)。 默认值是 "sendemail.thread" 配置值;如果未指定,则默认为 --thread 选项。 当git send-email 被要求添加 In-Reply-To 头信息时,用户应确保该头条信息不存在(特别要注意的是,git format-patch 可被配置为自行进行线程处理...
$ git commit -s -m "Add format strings for bb_error_msg_and_die" 4. Format a patch and send it out to the receiver: $ git format-patch -C -n master..$dev_branch $ git send-email --compose --no-chain-reply-to --suppress-from --to kernel@kernel.org 0001-*.patch...
用户需要确保在git send-email被要求添加 In-Reply-To 头时已经存在(特别是git format-patch可以配置为自己执行线程)。如果不这样做,可能无法在收件人的MUA中产生预期结果。 管理 --confirm=<mode> 在发送之前确认: always在发送之前会一直确认 never发送前绝不会确认 ...
git send-email --dump-aliases Composing: --from <str> * Email From: --[no-]to <str> * Email To: --[no-]cc <str> * Email Cc: --[no-]bcc <str> * Email Bcc: --subject <str> * Email "Subject:" --reply-to <str> * Email "Reply-To:" --in-reply-to <str...
When--composeis used, git send-email will use the From, To, Cc, Bcc, Subject, Reply-To, and In-Reply-To headers specified in the message. If the body of the message (what you type after the headers and a blank line) only contains blank (or Git: prefixed) lines, the summary won...
When--composeis used, git send-email will use the From, Subject, and In-Reply-To headers specified in the message. If the body of the message (what you type after the headers and a blank line) only contains blank (or Git: prefixed) lines, the summary won’t be sent, but From, ...
* "git send-email --in-reply-to=" did not use the In-Reply-To: header with the value given from the command line, and let it be overridden by the value on In-Reply-To: header in the messages being sent out (if exists).
基本信息 发布日期:2023-11-02(官方当地时间) 更新类型:普通更新 更新版本:Git v2.43.0-rc0 感知时间:2023-11-09 23:30:21 风险等级:未知 情报贡献:TSRC 来源链接 https://public-inbox.org/git/xmqqy1fgkqg1.fsf@gitster.g/ 更新标题 [ANNOUNCE] Git v2.43.0-rc0 ...
# Example reply to: #$initial_reply_to = ''; #<20050203173208.GA23964@foobar.com>';my $repo = eval { Git->repository() }; my @repo = $repo ? ($repo) : (); my $term = eval { $ENV{"GIT_SEND_EMAIL_NOTTY"} ? new Term::ReadLine 'git-send-email', \*STDIN, \*STDOUT...
followed by the diffs of files modified by the commit. The commit emails are threaded to the corresponding reference change email via "In-Reply-To". This style (similar to the "git format-patch" style used on the Git mailing list) makes it easy to scan through the emails, jump to patch...