From: dan <i@dan.games>
To: John Kehayias <john.kehayias@protonmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Philip McGrath <philip@philipmcgrath.com>,
Saku Laesvuori <saku@laesvuori.fi>,
69461@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>,
guix-devel@gnu.org, Attila Lendvai <attila@lendvai.name>
Subject: [bug#69461] Should commits rather be buildable or small
Date: Mon, 25 Mar 2024 11:23:55 +0800 [thread overview]
Message-ID: <cb447add-8add-47be-9728-b29c11b649cb@dan.games> (raw)
Message-ID: <20240325032355.qfRnj_aYp-3J8c_LZhMFU0XBlKM1pERhcym3HmfsmSE@z> (raw)
In-Reply-To: <87y1a7nmbx.fsf@protonmail.com>
Hi John,
On 3/25/2024 9:15 AM, John Kehayias wrote:
> dan: Do you know if just a version/hash bump is at least buildable? Or
> are the changes necessary for the packages to build/function at all?
> Or I guess if the non-version changes are applicable to the current
> version first?
I'll give it a try tomorrow. I think if packages are updated in certain
sequence, it should be at least buildable. I'll give update or send a
new patch series if I have any progress on this.
--
dan
next prev parent reply other threads:[~2024-03-25 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 8:42 Should commits rather be buildable or small Saku Laesvuori
2023-12-08 11:41 ` Tomas Volf
2023-12-08 12:05 ` Lars-Dominik Braun
2023-12-08 16:35 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-08 15:44 ` Liliana Marie Prikler
2023-12-10 15:28 ` Saku Laesvuori
2023-12-10 15:50 ` Liliana Marie Prikler
2023-12-10 17:02 ` Attila Lendvai
2023-12-10 17:50 ` Ricardo Wurmus
2023-12-10 23:20 ` Attila Lendvai
2023-12-10 23:56 ` Philip McGrath
2023-12-11 10:51 ` Attila Lendvai
2023-12-11 11:51 ` Ricardo Wurmus
2024-03-04 21:38 ` John Kehayias
2024-03-05 4:32 ` dan
2024-03-05 5:19 ` Liliana Marie Prikler
2024-03-25 1:15 ` John Kehayias
2024-03-25 3:23 ` dan [this message]
2024-03-25 3:23 ` [bug#69461] " dan
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=cb447add-8add-47be-9728-b29c11b649cb@dan.games \
--to=i@dan.games \
--cc=69461@debbugs.gnu.org \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=liliana.prikler@gmail.com \
--cc=philip@philipmcgrath.com \
--cc=rekado@elephly.net \
--cc=saku@laesvuori.fi \
/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).