From: Vasilii Smirnov via Guix-patches via <guix-patches@gnu.org>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 70615@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#70615] closed (Re: [bug#70615] [PATCH 0/2] Update haxe and hashlink)
Date: Fri, 3 May 2024 20:29:37 +0200 [thread overview]
Message-ID: <d747a478-e5a7-0b87-b189-cac83e2d0911@mailbox.org> (raw)
In-Reply-To: <878r0rrkzp.fsf@protonmail.com>
On 5/3/24 17:08, John Kehayias wrote:
> Just a heads up that these patches applied without full commit logs
> (which weren't included in the patches sent either). Patch 1 also
> affected 3 packages, maybe the haxe ones needed to be upgraded together
> (along with the ocaml-luv?) but that should have been noted (and
> probably still done separately).
>
> Thanks,
> John
Hi, John. I did add an explanation for ocaml-luv in the commit message
(git show 2205660ce2), but yeah, it's not in the ChangeLog format. Sorry
about that.
prev parent reply other threads:[~2024-05-04 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 20:08 [bug#70615] [PATCH 0/2] Update haxe and hashlink vasilii.smirnov--- via Guix-patches via
2024-04-28 7:27 ` [bug#70615] [PATCH 1/2] gnu: haxe: Update to 4.3.4 vasilii.smirnov--- via Guix-patches via
2024-04-28 7:27 ` [bug#70615] [PATCH 2/2] gnu: hashlink: Update to 1.14 vasilii.smirnov--- via Guix-patches via
2024-04-28 7:35 ` [bug#70615] [PATCH 0/2] Update haxe and hashlink Zheng Junjie
2024-04-28 7:44 ` Vasilii Smirnov via Guix-patches via
2024-04-28 14:45 ` bug#70615: " Maxim Cournoyer
2024-05-03 15:08 ` [bug#70615] closed (Re: [bug#70615] [PATCH 0/2] Update haxe and hashlink) John Kehayias via Guix-patches via
2024-05-03 18:29 ` Vasilii Smirnov via Guix-patches via [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=d747a478-e5a7-0b87-b189-cac83e2d0911@mailbox.org \
--to=guix-patches@gnu.org \
--cc=70615@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=vasilii.smirnov@mailbox.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).