Hello!
Christopher Baines skribis:
> Ludovic Courtès writes:
[...]
>> I would expect only patch submission info, and possibly commit
>> notifications, to be grabbed from email, while the rest would be
>> extracted from the repo, thereby hopefully limiting the risk of
>> misinterpreting email.
Ludovic Courtès writes:
>> As well as listening to the Guix Commits mailing list for emails about
>> new revisions, more of the information in these emails is now stored, in
>> particular, the time they were sent, and the branch the email applies
>> to. This can be seen on the new Branches page
Christopher Baines skribis:
>>>
>>> https://prototype-guix-data-service.cbaines.net/revision/f52e83470b05b2473ea13feb2842a1330c316a00/packages.json?field=version&field=synopsis&field=description&field=home-page&field=location&field=licenses&limit_results=9
>>
>> FWIW it is very slow.
This pa
Hi!
Christopher Baines skribis:
> Since then, I've made some more progress. There's a new statistics page
> [2]. I've got used to using Sqitch [3] to help manage the database
> schema, and I've added some basic tests.
The URL for [2] is actually:
https://prototype-guix-data-service.cbaines.n
Amirouche writes:
> On 2019-05-17 09:56, Christopher Baines wrote:
>> Hey,
>>
>> In summary, I think the Guix Data Service might be getting useful
>> enough
>> that setting it up properly might be a good next step, and I'd be
>> interested in what others think?
>
> Yeah. And it looks good :)
Th
On 2019-05-17 09:56, Christopher Baines wrote:
Hey,
In summary, I think the Guix Data Service might be getting useful
enough
that setting it up properly might be a good next step, and I'd be
interested in what others think?
Yeah. And it looks good :)
A bit over a month ago, I sent out an u
