From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: Konstantin Ryabitsev <mricon@kernel.org>,
Neal Caidin <ncaidin@linuxfoundation.org>
Cc: cip-members@lists.cip-project.org, Pavel Machek <pavel@ucw.cz>,
cip-dev@lists.cip-project.org, cip-board@lists.cip-project.org,
cip-security@lists.cip-project.org
Subject: Re: [cip-members] [cip-dev] Migration complete - Re: Mailman2 to Groups.io reminder
Date: Tue, 7 Apr 2020 17:17:44 +0200 [thread overview]
Message-ID: <eced03e3-465b-2b81-ee43-a78cce6ee35c@siemens.com> (raw)
In-Reply-To: <20200407151223.5nj4433u3il264zk@chatter.i7.local>
On 07.04.20 17:12, Konstantin Ryabitsev wrote:
> On Tue, Apr 07, 2020 at 08:58:31AM +0200, Jan Kiszka wrote:
>>
>> Konstantin, could you have a look or organize help? This is a blocker for
>> us, groups.io must not mess with messages.
>>
>> But given that other projects are using this workflow as well, I strongly
>> suspect there is a way to fix it.
>
> On each list's "Settings" page there is an option called:
>
> Separate Message Footers
> (Place message footers in a separate MIME part)
>
> That's the one you want enabled.
Perfect! Neal, you are admin? Can you change that?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4564): https://lists.cip-project.org/g/cip-dev/message/4564
Mute This Topic: https://lists.cip-project.org/mt/72845465/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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-04-07 15:17 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 [this message]
2020-04-07 15:40 ` Neal Caidin
2020-04-20 18:54 ` Pavel Machek
2020-04-07 7:09 ` Pavel Machek
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=eced03e3-465b-2b81-ee43-a78cce6ee35c@siemens.com \
--to=jan.kiszka@siemens.com \
--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=mricon@kernel.org \
--cc=ncaidin@linuxfoundation.org \
--cc=pavel@ucw.cz \
/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).