From: Maxime Devos <maximedevos@telenet.be>
To: bo0od <bo0od@riseup.net>, Leo Famulari <leo@famulari.name>
Cc: 47660@debbugs.gnu.org
Subject: bug#47660: Add link to the ticket when someone reply
Date: Sat, 10 Apr 2021 12:45:26 +0200 [thread overview]
Message-ID: <ce761b2c96ada1f4beadc36ed040e62c796aa2d2.camel@telenet.be> (raw)
In-Reply-To: <3fc025b1-aa56-aec6-5c0a-80f8562f0e8e@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
On Fri, 2021-04-09 at 20:44 +0000, bo0od wrote:
> This work or i search for it also work, But we are talking making things
> much easier and its possible through providing the link directly to the
> ticket in bottom, I believe this practice followed by all major
> ticketing systems,platforms,projects.. So i dont understand whats the
> big deal having it here as well.
Mangling e-mails can cause all kinds of trouble.
It would mess up git patches, break messages signed with PGP or S/MIME
(does anyone here actually use S/MIME?), makes some headers used for
spam detection (and more generally, detecting forged mails) invalid,
which will lead to messages from the mailing list and @debbugs.gnu.org
be marked as spam ...
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-04-10 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 17:38 bug#47660: Add link to the ticket when someone reply bo0od
2021-04-08 18:45 ` Leo Famulari
2021-04-09 20:44 ` bo0od
2021-04-10 10:45 ` Maxime Devos [this message]
2021-04-10 14:20 ` bo0od
2021-04-10 16:44 ` Maxime Devos
2021-04-10 20:13 ` bo0od
2021-04-15 14:24 ` Bonface Munyoki K.
2021-04-15 17:00 ` bo0od
2021-04-15 17:51 ` Maxime Devos
2021-04-16 2:38 ` bo0od
2022-03-18 2:56 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce761b2c96ada1f4beadc36ed040e62c796aa2d2.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=47660@debbugs.gnu.org \
--cc=bo0od@riseup.net \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).