From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Broken build notification from debian salsa
Date: Tue, 7 Apr 2020 09:00:06 -0700
Message-ID: <CAC2bXD4K5p+_ar__mz02WQ+hrxZe08CR0mH9t0_99vWUrQTJ0w@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDzpR4HEg+zOZ1AVvEYdwmm=YWmv0PTwMkDN84-wkyF3Dg@mail.gmail.com>
On Tue, Apr 7, 2020, 08:53 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Tue, Apr 7, 2020 at 4:47 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
>
> > a separate list can be set up, one that is admin-moderator-only, no
> > subscribes or unsubscribes permitted.
>
> hm that wouldn't work, would it... hmm...
I'm thinking what will work best is just to build our own system that uses
the gitlab api to monitor builds and send emails CCed to the committer and
to a mailing list. neither are currently supported by gitlab, it currently
sends them all to me since I registered the ssh key for the git mirroring
cron job.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 14:37 Jacob Lifshay
2020-04-07 15:00 ` Luke Kenneth Casson Leighton
2020-04-07 15:13 ` Jacob Lifshay
2020-04-07 15:47 ` Luke Kenneth Casson Leighton
2020-04-07 15:52 ` Luke Kenneth Casson Leighton
2020-04-07 16:00 ` Jacob Lifshay [this message]
2020-04-07 16:41 ` Jacob Lifshay
2020-04-07 16:52 ` Luke Kenneth Casson Leighton
2020-04-08 15:42 ` [libre-riscv-dev] GitLab CI Archiver Jacob Lifshay
2020-04-08 16:15 ` Luke Kenneth Casson Leighton
2020-04-09 20:25 ` Jacob Lifshay
2020-04-07 15:03 ` [libre-riscv-dev] Broken build notification from debian salsa Immanuel, Yehowshua U
2020-04-07 15:10 ` Luke Kenneth Casson Leighton
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=CAC2bXD4K5p+_ar__mz02WQ+hrxZe08CR0mH9t0_99vWUrQTJ0w@mail.gmail.com \
--to=programmerjake@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git