From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: [PATCH 1/2] Support publishing build events
Date: Wed, 08 Jan 2020 12:27:22 +0100 [thread overview]
Message-ID: <877e22fasl.fsf@gnu.org> (raw)
In-Reply-To: <871rsoryrg.fsf@cbaines.net> (Christopher Baines's message of "Sat, 28 Dec 2019 20:17:07 +0000")
Hi!
Christopher Baines <mail@cbaines.net> skribis:
> I've finally got back around to looking at this again, I've sent a new
> v4 version which is a slimmed down version of the previous patch. The
> events table itself is now used as the queue, with sent events being
> deleted. The table is also only populated if the --record-events option
> is set when running Cuirass.
It’s been a while already; I’d say this v4 can go in, and we can always
adjust later if needed!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-01-08 11:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 7:41 Getting build information in to the Guix Data Service (draft patch) Christopher Baines
2019-10-20 7:49 ` [PATCH] Support publishing build events Christopher Baines via Development of GNU Guix and the GNU System distribution.
2019-10-21 9:31 ` Mathieu Othacehe
2019-10-21 21:47 ` Christopher Baines
2019-10-23 14:39 ` Getting build information in to the Guix Data Service (draft patch) Ludovic Courtès
2019-10-23 23:32 ` Christopher Baines
2019-10-28 8:10 ` [PATCH 1/2] Support publishing build events Christopher Baines
2019-10-28 8:10 ` [PATCH 2/2] Support publishing evaluation events Christopher Baines
2019-11-16 21:41 ` Ludovic Courtès
2019-11-16 23:34 ` Christopher Baines
2019-11-16 21:39 ` [PATCH 1/2] Support publishing build events Ludovic Courtès
2019-11-16 23:13 ` Christopher Baines
2019-11-17 21:26 ` Ludovic Courtès
2019-11-18 8:53 ` Christopher Baines
2019-11-28 18:36 ` Christopher Baines
2019-11-28 18:36 ` [PATCH 2/2] Support publishing evaluation events Christopher Baines
2019-11-30 14:10 ` Clément Lassieur
2019-12-03 0:21 ` Christopher Baines
2019-11-30 14:08 ` [PATCH 1/2] Support publishing build events Clément Lassieur
2019-12-03 0:12 ` Christopher Baines
2019-12-03 11:25 ` Clément Lassieur
2019-12-03 19:44 ` Christopher Baines
2019-12-04 13:59 ` Clément Lassieur
2019-12-28 20:17 ` Christopher Baines
2020-01-08 11:27 ` Ludovic Courtès [this message]
2020-01-16 8:37 ` Christopher Baines
2019-11-30 14:23 ` Clément Lassieur
2019-12-03 0:20 ` Christopher Baines
2019-11-28 18:48 ` Christopher Baines
2019-11-30 11:15 ` Clément Lassieur
2019-12-02 23:22 ` Christopher Baines
2019-10-28 8:33 ` Getting build information in to the Guix Data Service (draft patch) Christopher Baines
2019-12-28 19:05 ` [PATCH v3 1/2] Support publishing build events Christopher Baines
2019-12-28 19:05 ` [PATCH v3 2/2] Support publishing evaluation events Christopher Baines
2019-12-28 19:54 ` [PATCH v4 1/2] Support publishing build events Christopher Baines
2019-12-28 19:54 ` [PATCH v4 2/2] Support publishing evaluation events 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e22fasl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=clement@lassieur.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.