all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guillaume LE VAILLANT <glv@posteo.net>, 36071@debbugs.gnu.org
Subject: [bug#36071] [PATCH] gnu: Add leela-zero.
Date: Wed, 12 Jun 2019 00:54:19 +0200	[thread overview]
Message-ID: <87h88vens4.fsf@nckx> (raw)
In-Reply-To: <87lfy7alke.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

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

I can't assess its accuracy, but this comment[0] from the linked 
LWN article looks relevant.  Particularly:

--8<---------------cut here---------------start------------->8---
So this is basically a distributed computing client as well as a 
Go
engine that runs with the results of that distributed computing 
effort.
--8<---------------cut here---------------end--------------->8---

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.

Kind regards,

T G-R

[0]: https://lwn.net/Articles/760483/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-06-11 23:06 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 [this message]
2019-06-25 15:12         ` bug#36071: " Ludovic Courtès

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=87h88vens4.fsf@nckx \
    --to=me@tobias.gr \
    --cc=36071@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 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.