From: Andreas Enge <andreas@enge.fr>
To: 67873-done@debbugs.gnu.org
Subject: bug#67873: Close
Date: Fri, 8 Mar 2024 11:12:30 +0100 [thread overview]
Message-ID: <ZerkjqWEH0CvZ89p@jurong> (raw)
In-Reply-To: <c11efe92c927b3e4eccf08102eb4c7e690986ecc.1702861753.git.atai@atai.org>
Hello Andy,
I am closing this as a similar patch has been applied already:
commit 6e7484808fa2979bd686aae5b64a71849e9391b9
Author: John Fremlin <john@fremlin.org>
Date: Tue Feb 13 10:32:12 2024 -0500
gnu: llama-cpp: Update to 03bf16.
* gnu/packages/machine-learning.scm (llama-cpp): Update to
03bf161eb6dea6400ee49c6dc6b69bdcfa9fd3fc.
[arguments]: Adjust program names.
Change-Id: I9f5474606dd01be73fbc50813250991e9d248d85
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Probably your commit is more recent; at the same time for a project
without releases or meaningful tags or branches, it is difficult to tell
when we should update, and there is no point in updating all the time.
I would say after a "meaningful" change, to be determined by users of the
software, for instance.
Thanks,
Andreas
prev parent reply other threads:[~2024-03-08 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 1:09 [bug#67873] [PATCH] llama-cpp: Update to commit 2994f0 Andy Tai
2024-01-01 2:02 ` [bug#67873] [PATCH v2] " Andy Tai
2024-02-27 5:29 ` [bug#67873] [PATCH v3] llama-cpp: Update to commit de473f Andy Tai
2024-03-08 10:12 ` Andreas Enge [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=ZerkjqWEH0CvZ89p@jurong \
--to=andreas@enge.fr \
--cc=67873-done@debbugs.gnu.org \
/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).