unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guillaume LE VAILLANT <glv@posteo.net>, 36071-done@debbugs.gnu.org
Subject: bug#36071: [PATCH] gnu: Add leela-zero.
Date: Tue, 25 Jun 2019 17:12:01 +0200	[thread overview]
Message-ID: <87lfxplmwu.fsf@gnu.org> (raw)
In-Reply-To: <87lfy7alke.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 11 Jun 2019 22:55:45 +0200")

Hello!

Ricardo Wurmus <rekado@elephly.net> skribis:

> Back to this patch: I think it’s fine to accept it as long as the
> software necessary for training is included.

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> I can't assess its accuracy, but this comment[0] from the linked 
> LWN article looks relevant.  Particularly:
>
> So this is basically a distributed computing client as well as a 
> Go
> engine that runs with the results of that distributed computing 
> effort.
>
> If that's true, there is no separate ‘training software’ to worry 
> about.
>
> The whole link is worth a click since there seems to be a ‘server 
> component’ involved as well.

Based on the info we have so far, including the fact that Debian
includes it (see <https://packages.debian.org/leela-zero>), I went ahead
and applied the patch.

We can obviously revisit this issue later should someone have concerns
and/or additional info.

Thanks everyone!

Ludo’.

      parent reply	other threads:[~2019-06-25 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 13:06 [bug#36071] [PATCH] gnu: Add leela-zero Guillaume LE VAILLANT
2019-06-05 15:24 ` Ludovic Courtès
2019-06-05 17:26   ` Guillaume LE VAILLANT
2019-06-05 20:47     ` Ludovic Courtès
2019-06-06 10:38       ` zimoun
2019-06-11 20:55       ` Ricardo Wurmus
2019-06-11 22:54         ` Tobias Geerinckx-Rice
2019-06-25 15:12         ` Ludovic Courtès [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

  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=87lfxplmwu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36071-done@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=rekado@elephly.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).