From: Andrew Hyatt <ahyatt@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: rms@gnu.org, jporterbugs@gmail.com, emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: llm
Date: Tue, 19 Sep 2023 12:26:28 -0400 [thread overview]
Message-ID: <CAM6wYYKuqDjHy8MX8wWFDreW=moABfF9Ofit8RDJn_bKznN9=w@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnWic_qsz3fHv7ng75vxFyDR4K99jTF3k5RDK8+gfs-1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
I've submitted the configuration for llm and set up the branch from my
repository last Friday. However, I'm still not seeing this package being
reflected in GNU ELPA's package archive. I followed the instructions, but
perhaps there's some step that I've missed, or it is only periodically
rebuilt?
On Tue, Sep 12, 2023 at 11:05 AM Stefan Kangas <stefankangas@gmail.com>
wrote:
> Andrew Hyatt <ahyatt@gmail.com> writes:
>
> > Another question is whether this should be one package or many. The
> > many-package option would have the llm and llm-fake package in the main
> llm
> > package, with a package for all llm clients, such as llm-openai and
> > llm-vertex (which are the two options I have now). If someone has an
> > opinion on this, please let me know.
>
> It's easier for users if it's just one package.
>
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
next prev parent reply other threads:[~2023-09-19 16:26 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 23:54 [NonGNU ELPA] New package: llm Andrew Hyatt
2023-08-08 5:42 ` Philip Kaludercic
2023-08-08 15:08 ` Spencer Baugh
2023-08-08 15:09 ` Andrew Hyatt
2023-08-09 3:47 ` Richard Stallman
2023-08-09 4:37 ` Andrew Hyatt
2023-08-13 1:43 ` Richard Stallman
2023-08-13 1:43 ` Richard Stallman
2023-08-13 2:11 ` Emanuel Berg
2023-08-15 5:14 ` Andrew Hyatt
2023-08-15 17:12 ` Jim Porter
2023-08-17 2:02 ` Richard Stallman
2023-08-17 2:48 ` Andrew Hyatt
2023-08-19 1:51 ` Richard Stallman
2023-08-19 9:08 ` Ihor Radchenko
2023-08-21 1:12 ` Richard Stallman
2023-08-21 8:26 ` Ihor Radchenko
2023-08-17 17:08 ` Daniel Fleischer
2023-08-19 1:49 ` Richard Stallman
2023-08-19 8:15 ` Daniel Fleischer
2023-08-21 1:12 ` Richard Stallman
2023-08-21 4:48 ` Jim Porter
2023-08-21 5:12 ` Andrew Hyatt
2023-08-21 6:03 ` Jim Porter
2023-08-21 6:36 ` Daniel Fleischer
2023-08-22 1:06 ` Richard Stallman
2023-08-16 2:30 ` Richard Stallman
2023-08-16 5:11 ` Tomas Hlavaty
2023-08-18 2:10 ` Richard Stallman
2023-08-27 1:07 ` Andrew Hyatt
2023-08-27 13:11 ` Philip Kaludercic
2023-08-28 1:31 ` Richard Stallman
2023-08-28 2:32 ` Andrew Hyatt
2023-08-28 2:59 ` Jim Porter
2023-08-28 4:54 ` Andrew Hyatt
2023-08-31 2:10 ` Richard Stallman
2023-08-31 9:06 ` Ihor Radchenko
2023-08-31 16:29 ` chad
2023-09-01 9:53 ` Ihor Radchenko
2023-09-04 1:27 ` Richard Stallman
2023-09-04 1:27 ` Richard Stallman
2023-09-06 12:25 ` Ihor Radchenko
2023-09-06 12:51 ` Is ChatGTP SaaSS? (was: [NonGNU ELPA] New package: llm) Ihor Radchenko
2023-09-06 16:59 ` Andrew Hyatt
2023-09-09 0:37 ` Richard Stallman
2023-09-06 22:52 ` Emanuel Berg
2023-09-07 7:28 ` Lucien Cartier-Tilet
2023-09-07 7:57 ` Emanuel Berg
2023-09-09 0:38 ` Richard Stallman
2023-09-09 10:28 ` Collaborative training of Libre LLMs (was: Is ChatGTP SaaSS? (was: [NonGNU ELPA] New package: llm)) Ihor Radchenko
2023-09-09 11:19 ` Jean Louis
2023-09-10 0:22 ` Richard Stallman
2023-09-10 2:18 ` Debanjum Singh Solanky
2023-08-27 18:36 ` [NonGNU ELPA] New package: llm Jim Porter
2023-08-28 0:19 ` Andrew Hyatt
2023-09-04 1:27 ` Richard Stallman
2023-09-04 5:18 ` Andrew Hyatt
2023-09-07 1:21 ` Richard Stallman
2023-09-12 4:54 ` Andrew Hyatt
2023-09-12 9:57 ` Philip Kaludercic
2023-09-12 15:05 ` Stefan Kangas
2023-09-19 16:26 ` Andrew Hyatt [this message]
2023-09-19 16:34 ` Philip Kaludercic
2023-09-19 18:19 ` Andrew Hyatt
2023-09-04 1:27 ` Richard Stallman
2023-08-09 3:47 ` Richard Stallman
2023-08-09 4:06 ` Andrew Hyatt
2023-08-12 2:44 ` Richard Stallman
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='CAM6wYYKuqDjHy8MX8wWFDreW=moABfF9Ofit8RDJn_bKznN9=w@mail.gmail.com' \
--to=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.