Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
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 16:10:12 +0100
Message-ID: <CAPweEDwAYx29D2YurFP5nRM-G7=2Vzb8Wnxx5jiMXgoe+QL8TQ@mail.gmail.com> (raw)
In-Reply-To: <A0849B16-A2AD-47A1-9622-7DA77EDC7EF1@gatech.edu>

On Tue, Apr 7, 2020 at 4:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> >  We
> > should probably figure out how to get salsa build failures sent to the
> > mailing list as well, though we'd have to remove the unsubscribe link to
> > prevent accidental/malicious unsubscription.
>
> I think we had talked about creating another mailing list for builds and bugs.
> Now might be a good time to set that up.

https://bugs.libre-soc.org/show_bug.cgi?id=184

best discussed there.

> The three mailing lists discussed were
>  - main/dev
>  - bugs
>  - watercooler

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      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
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 [this message]

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='CAPweEDwAYx29D2YurFP5nRM-G7=2Vzb8Wnxx5jiMXgoe+QL8TQ@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --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