From: Xinglu Chen <public@yoctocell.xyz>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Security related tooling project
Date: Sun, 04 Apr 2021 12:43:16 +0200 [thread overview]
Message-ID: <87pmzauy7v.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87v992314x.fsf@cbaines.net>
On Sun, Apr 04 2021, Christopher Baines wrote:
> Cool :) While it's not directly security related, I really want the
> subscriptions functionality I'm planning to work on to be done so that
> people can subscribe to things related to the packages they use, like
> new versions becoming available, or the build breaking for example, as
> that might help people stay involved.
A bit off-topic, but I think it would be nice if the Emails/RSS feeds
would contain more information. Right now it just says that PACKAGE on
ARCHITECTURE is fixed/broken, and gives a URL pointing to the build job.
I think it would be useful to also show the commit (the revision and
the commit summary for some context) that caused the fix/failure, and
maybe also the time it took to build the package, plus a link to the raw
build log.
All of this sounds very exciting. Keep up the great work!
next prev parent reply other threads:[~2021-04-04 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 10:41 Security related tooling project Christopher Baines
2021-04-03 16:13 ` Security related tooling project OFF TOPIC PRAISE Joshua Branson
2021-04-04 8:17 ` Christopher Baines
2021-04-04 13:35 ` Joshua Branson
2021-04-03 21:44 ` Security related tooling project Léo Le Bouter
2021-04-04 8:24 ` Christopher Baines
2021-04-04 5:09 ` Chris Marusich
2021-04-04 8:27 ` Christopher Baines
2021-04-04 10:43 ` Xinglu Chen [this message]
2021-04-04 20:32 ` Chris Marusich
2021-04-17 15:20 ` Ludovic Courtès
2021-04-18 2:49 ` Bengt Richter
2021-04-23 20:34 ` Christopher Baines
2021-04-23 20:32 ` Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmzauy7v.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).