From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] gitlab-ci-archiver status
Date: Thu, 9 Apr 2020 13:31:08 -0700
Message-ID: <CAC2bXD6cgfvQFPkjS6vabYUJERd2ZPV+9oyP3+O8A2ApmK2XPg@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDwnXBeRzMMJmcuZAsR1hOec=Xx6kvmsuYasO_sDYr82Gw@mail.gmail.com>
On Thu, Apr 9, 2020, 13:25 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Thu, Apr 9, 2020 at 9:03 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> > It also needs code to send out the build failure emails, or that could be
> > done by a shell script by parsing all the new commits -- so an hour of
> work
> > in either bash or Rust
>
> the general UNIX philosohpy is that one program do one task and do it
> well. therefore farm that task to an external program.
>
Ok, though both of calling out to sendmail with all the correct parameters
or writing an external script to parse the commits and then call sendmail
are likely to require much more code than just calling a library like
lettre.at even with the additional code for reading the config options from
the config file.
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: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 19:21 [libre-riscv-dev] more build failures Jacob Lifshay
2020-04-09 19:31 ` Luke Kenneth Casson Leighton
2020-04-09 20:03 ` [libre-riscv-dev] gitlab-ci-archiver status Jacob Lifshay
2020-04-09 20:24 ` Luke Kenneth Casson Leighton
2020-04-09 20:31 ` Jacob Lifshay [this message]
2020-04-09 21:48 ` Luke Kenneth Casson Leighton
2020-04-09 21:54 ` Jacob Lifshay
2020-04-09 23:19 ` Luke Kenneth Casson Leighton
2020-04-10 1:56 ` Luke Kenneth Casson Leighton
2020-04-10 2:27 ` Jacob Lifshay
2020-04-10 12:08 ` Luke Kenneth Casson Leighton
2020-04-10 17:15 ` Jacob Lifshay
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=CAC2bXD6cgfvQFPkjS6vabYUJERd2ZPV+9oyP3+O8A2ApmK2XPg@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