From: Andy Tai <atai@atai.org>
To: guile-devel@gnu.org
Subject: Re: role of core-updates
Date: Sun, 26 Nov 2023 22:52:26 -0800 [thread overview]
Message-ID: <CAJsg1E-se1ZEbePeOZe0RPzaKq0qxMGdoh30+evKZhXqspbSKA@mail.gmail.com> (raw)
In-Reply-To: <CAJsg1E9fgE3rwFkhY2po98cAQ5pF1WpGL-PodR1maVC8Kc6HZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
Sorry... this was sent to the wrong list. Meant to the guix devel list.
Sorry for the wrong post here.
On Sun, Nov 26, 2023 at 10:10 PM Andy Tai <atai@atai.org> wrote:
> Hi, hope Guix maintainers can clarify the role of the now core-updates
> branch; the current documentation does not specify the core-updates
> branch as a thing but there are clearly interests and uses of this
> branch for package updates not belonging to a feature branch like
> gnome and it is useful for, say, updating to the GNU make package
> which would have caused world rebuild. Thanks
>
[-- Attachment #2: Type: text/html, Size: 986 bytes --]
prev parent reply other threads:[~2023-11-27 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 6:10 role of core-updates Andy Tai
2023-11-27 6:52 ` Andy Tai [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJsg1E-se1ZEbePeOZe0RPzaKq0qxMGdoh30+evKZhXqspbSKA@mail.gmail.com \
--to=atai@atai.org \
--cc=guile-devel@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.
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).