all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Ryan Prior <rprior@protonmail.com>
Cc: 41010-done@debbugs.gnu.org
Subject: bug#41010: [PATCH 0/1] Updated patch for 0.8.pre5
Date: Fri, 29 May 2020 06:48:22 +0200	[thread overview]
Message-ID: <87r1v32vop.fsf@nckx> (raw)
In-Reply-To: <20200528233825.15320-1-rprior@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Ryan,

Ryan Prior via Guix-patches via 写道:
> The best upstream release is now 0.8.pre5, so here's a patch 
> updated for that version.

Pushed as 01914fd2bbad199df89b1cac2c72b453e57685ff with a 
completed commit message and the previously suggested gcc → $CC 
change.

Thanks!

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2020-05-29  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 20:01 [bug#41010] Rename & upgrade oil-shell Ryan Prior via Guix-patches via
2020-05-01 21:01 ` [bug#41010] Upgrade Oil to 0.8.pre4 Ryan Prior via Guix-patches via
2020-05-01 23:23   ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-01 23:33     ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-02  4:02     ` Ryan Prior via Guix-patches via
2020-05-15 17:10       ` Ryan Prior via Guix-patches via
2020-05-15 18:31       ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-16 11:20       ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-17  6:14         ` Ryan Prior via Guix-patches via
2020-05-02 19:16     ` Leo Famulari
2020-05-28 23:38 ` [bug#41010] [PATCH 0/1] Updated patch for 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-28 23:38   ` [bug#41010] [PATCH 1/1] gnu: oil: Update to 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-29  4:48   ` Tobias Geerinckx-Rice 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1v32vop.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=41010-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=rprior@protonmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.