From: Aditya Garg <gargaditya08@live.com>
To: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
"sandals@crustytoothpaste.net" <sandals@crustytoothpaste.net>,
Julian Swagemakers <julian@swagemakers.org>,
Zi Yao <ziyao@disroot.org>, Jeff King <peff@peff.net>,
Jacob Keller <jacob.e.keller@intel.com>
Subject: [PATCH v3 0/2] send-email: fix threads breaking in case user edits emails and improvements to outlook ID fix.
Date: Sun, 25 May 2025 17:12:16 +0000 [thread overview]
Message-ID: <cover.1748192784.git.gargaditya08@live.com> (raw)
In-Reply-To: <20250524123911.1160-1-gargaditya08@live.com>
Hi all,
This patch series fixes two minor issues with git-send-email.
The first patch fixes a bug that caused the message number to increase
when a user edits an email. As a result of this bug, threads would
break when a user edits an email.
The second patch improves the logging of the new message ID assigned by
Outlook when a user edits an email.
Aditya Garg (2):
send-email: fix bug resulting in increased message number if a message
is edited
send-email: show the new message id assigned by outlook in the logs
git-send-email.perl | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
--
2.43.0
next prev parent reply other threads:[~2025-05-25 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 15:36 [PATCH] send-email: fix bug breaking shallow threading if the first patch is edited Aditya Garg
2025-05-23 15:44 ` Aditya Garg
2025-05-23 22:19 ` Junio C Hamano
2025-05-23 23:37 ` Jacob Keller
2025-05-24 12:39 ` [PATCH v2] send-email: fix bug resulting in increased message number if a message " Aditya Garg
2025-05-25 17:12 ` Aditya Garg [this message]
2025-05-25 17:12 ` [PATCH v3 1/2] " Aditya Garg
2025-05-25 18:49 ` Kristoffer Haugsbakk
2025-05-26 15:54 ` Aditya Garg
2025-05-25 17:12 ` [PATCH v3 2/2] send-email: show the new message id assigned by outlook in the logs Aditya Garg
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=cover.1748192784.git.gargaditya08@live.com \
--to=gargaditya08@live.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.e.keller@intel.com \
--cc=julian@swagemakers.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.com \
--cc=ziyao@disroot.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 NNTP newsgroup(s).