all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Roman Scherer <roman@burningswell.com>
Cc: 70584@debbugs.gnu.org,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Andrew Tropin <andrew@trop.in>
Subject: [bug#70584] [PATCH] gnu: Add emacs-llm.
Date: Sat, 27 Apr 2024 00:46:55 +0200	[thread overview]
Message-ID: <d1b4603466eb195361fa35eafe6561979a20cc0a.camel@gmail.com> (raw)
In-Reply-To: <CAEc_D28NhfpTrrHS_M8SGVii8eNtPb9V4cQvrdxUXo=2R3i+Pw@mail.gmail.com>

Am Samstag, dem 27.04.2024 um 00:35 +0200 schrieb Roman Scherer:
> Hi Liliana,
> I'm not sure if I understand your message. Do you say Guix does not
> want to package this?
> This is a package you can use with Ollama and is packaged on GNU ELPA
> as well.
> Greetings, Roman.
I'm not aware of the quality control procedures at ELPA, but if you
copied that bit from the description, they might have overlooked some
README nastiness.

As far as the functionality is concerned, by all means add it, but we
have principles here, even if they permit calling out to dubious APIs.

Cheers




  reply	other threads:[~2024-04-26 22:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  7:04 [bug#70584] [PATCH] gnu: Add emacs-llm Roman Scherer
2024-04-26 17:00 ` Liliana Marie Prikler
2024-04-26 22:35   ` Roman Scherer
2024-04-26 22:46     ` Liliana Marie Prikler [this message]
2024-04-26 23:05       ` Roman Scherer
2024-04-26 23:45         ` Liliana Marie Prikler
2024-04-27  7:20           ` Roman Scherer
2024-04-27  7:13 ` [bug#70584] [PATCH v2] " Roman Scherer
2024-04-29 18:40   ` Liliana Marie Prikler
2024-05-01 10:41     ` Roman Scherer
2024-05-01 10:40 ` [bug#70584] [PATCH v3] " Roman Scherer
2024-05-09  9:52   ` bug#70584: " Liliana Marie Prikler

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=d1b4603466eb195361fa35eafe6561979a20cc0a.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=70584@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=roman@burningswell.com \
    /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.