unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn via Guix-patches via <guix-patches@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 66731-done@debbugs.gnu.org, 66731@debbugs.gnu.org
Subject: [bug#66731] [PATCH] gnu: wine and wine64: Update to 8.18.
Date: Fri, 03 Nov 2023 16:19:24 +0000	[thread overview]
Message-ID: <0wHPwh3Ui-z-ukOWh0T8JMkvjb40LvkMvDb4RKKhqfyai1avcDoyUzXw87pO4vgIAuWa_FsLNwgVg95Vf7K9ecU0W1qs1HG_hqBGi51XUUI=@protonmail.com> (raw)
In-Reply-To: <875y2jm8r7.fsf@cbaines.net>


------- Original Message -------
On Friday, November 3rd, 2023 at 3:27 AM, Christopher Baines <mail@cbaines.net> wrote:


> 
> 
> 
> Kaelyn Takata via Guix-patches via guix-patches@gnu.org writes:
> 
> > * gnu/packages/wine.scm (wine-minimal): Update to 8.18.
> > [properties]: Set upstream-name.
> > 
> > Change-Id: I018c320a990bf101d193095b68c44312ce9653a4
> > ---
> > gnu/packages/wine.scm | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> 
> 
> Thanks for the patch! I tweaked the commit message to say wine-minimal
> rather than wine and wine64, since that's where the change is being
> made, and pushed this to master as
> ada7e0d04286d800197cc06752ea1b4a0f8a91d0.
> 
> Chris

Sounds good, thank you! I titled it as wine and wine64 as:
a) that was how commit a965ff448d updating the packages to 8.16 was titled, and
b) updating the version of wine-minimal also updates the version of wine and wine64 because of how the package definitions are structured, and wine and wine64 are the user-facing packages.

Cheers,
Kaelyn




      reply	other threads:[~2023-11-03 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 17:36 [bug#66731] [PATCH] gnu: wine and wine64: Update to 8.18 Kaelyn Takata via Guix-patches via
2023-11-03 10:27 ` Christopher Baines
2023-11-03 16:19   ` Kaelyn 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='0wHPwh3Ui-z-ukOWh0T8JMkvjb40LvkMvDb4RKKhqfyai1avcDoyUzXw87pO4vgIAuWa_FsLNwgVg95Vf7K9ecU0W1qs1HG_hqBGi51XUUI=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=66731-done@debbugs.gnu.org \
    --cc=66731@debbugs.gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=mail@cbaines.net \
    /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).