From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: patchwork and a proper archive
Date: Tue, 19 Jul 2022 17:08:58 +0200 [thread overview]
Message-ID: <20220719170850.5727e815@md1za8fc.ad001.siemens.net> (raw)
Hi guys,
as the community is getting bigger there are more and more people that
also want to try patches from the ML. That alone is impossible if one
is not subscribed, and can even be complicated in corporate email
environments ... outlook and git-am are not best friends and some
people use outlook.
So that calls for a second archive, one that allows to download mboxes.
And we had the discussion with that patchwork before, that would add
even more value as it will hopefully reduce the chance of MRs being
overlooked or forgotten about.
Jan mentioned that one can potentially get a lot of infra if one is
willing to do a full switch to another domain. Not sure that is the
best idea, but i personally would not mind.
Henning
next reply other threads:[~2022-07-19 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 15:08 Henning Schild [this message]
2022-07-19 15:50 ` Baurzhan Ismagulov
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=20220719170850.5727e815@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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