From: Pavel Machek <pavel@ucw.cz>
To: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
Cc: cip-dev@lists.cip-project.org, cip-board@lists.cip-project.org,
cip-members@lists.cip-project.org,
cip-security@lists.cip-project.org
Subject: Re: [cip-dev] Migration complete - Re: Mailman2 to Groups.io reminder
Date: Tue, 7 Apr 2020 09:09:14 +0200 [thread overview]
Message-ID: <20200407070914.GA17953@amd.ucw.cz> (raw)
In-Reply-To: <874ktwysrj.fsf@kokedama.swc.toshiba.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Hi!
> > They seem to add this kind of trailer to the messages, breaking GPG
> > signatures :-(.
> >
> > (I won't quote full trailer as it seems to contain some secrets?)
>
> I wonder if it's possible to turn these off by the admin.
>
> Also, another thing to test is the impact of the footer on applying
> patches sent via email (git am / git apply).
I suspect footer won't cause problems with patches; there are many
lists that add such footers, and patches normally survive that okay.
But our project is quite security-focused, so it would be good to
preserve GPG signatures...
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4562): https://lists.cip-project.org/g/cip-dev/message/4562
Mute This Topic: https://lists.cip-project.org/mt/72837893/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-04-07 11:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 20:56 [cip-dev] Mailman2 to Groups.io reminder Neal Caidin
2020-04-06 19:34 ` Neal Caidin
2020-04-06 21:45 ` [cip-dev] Migration complete - " Neal Caidin
2020-04-06 22:43 ` Pavel Machek
2020-04-07 1:44 ` punit1.agrawal
2020-04-07 6:58 ` [cip-members] " Jan Kiszka
2020-04-07 15:12 ` Konstantin Ryabitsev
2020-04-07 15:17 ` Jan Kiszka
2020-04-07 15:40 ` Neal Caidin
2020-04-20 18:54 ` Pavel Machek
2020-04-07 7:09 ` Pavel Machek [this message]
2020-04-07 7:18 ` [cip-dev] [cip-members] " Chris Paterson
2020-04-07 10:26 ` Urs Gleim
2020-04-07 11:39 ` Password reset - " Neal Caidin
2020-04-09 15:26 ` Chris Paterson
2020-04-09 17:17 ` [cip-dev] [cip-board] " Neal Caidin
2020-04-20 13:50 ` [cip-dev] " Neal Caidin
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=20200407070914.GA17953@amd.ucw.cz \
--to=pavel@ucw.cz \
--cc=cip-board@lists.cip-project.org \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@lists.cip-project.org \
--cc=cip-security@lists.cip-project.org \
--cc=punit1.agrawal@toshiba.co.jp \
/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).