unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: amirouche@hyper.dev
Cc: Ricardo Wurmus <rekado@elephly.net>, 35518-done@debbugs.gnu.org
Subject: bug#35518: gnu: guile-pfds bugfix
Date: Tue, 13 Jul 2021 22:43:44 -0400	[thread overview]
Message-ID: <878s29r4wv.fsf_-_@gmail.com> (raw)
In-Reply-To: <053f858c51866da5ffe2ed2b85f58d9d@hyper.dev> (amirouche@hyper.dev's message of "Mon, 06 May 2019 14:42:45 +0200")

amirouche@hyper.dev writes:

> On 2019-05-06 13:09, Ricardo Wurmus wrote:
>> amirouche@hyper.dev writes:
>> 
>>> Forgo the first, this patch is not perfect because It doesn't force an
>>> update.
>> The attached patch is more than 15MB in size.  I haven’t looked at
>> it
>> but I guess that’s not correct.
>
> I am not sure which patch you are referring to.
>
> Here is another patch. I followed the "Submitting Patches" section
> from the manual.

Applied as 51194ca1e845d5f3954cb9dd1fef79e930dc3777, adding only the
patching phase with an explanatory comment.

Thanks!

Closing.

Maxim




  parent reply	other threads:[~2021-07-14  2:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  0:52 [bug#35518] gnu: guile-pfds bugfix amirouche
2019-05-01  3:42 ` [bug#35518] (no subject) amirouche
2019-05-06 11:09   ` Ricardo Wurmus
2019-05-06 12:42     ` [bug#35518] [PATCH] fix guile-pfds bug amirouche
2019-05-06 13:10       ` Ricardo Wurmus
2021-07-14  2:43       ` Maxim Cournoyer [this message]
2019-05-01  6:20 ` [bug#35518] gnu: guile-pfds bugfix Ricardo Wurmus
2019-05-01 10:58   ` amirouche
2019-05-01 11:46   ` amirouche
2019-05-06  8:05     ` Ludovic Courtès
2019-05-06  8:05     ` Ludovic Courtès
2019-06-26  1:47 ` [bug#35518] upstream unresponsive Amirouche
2020-06-06  3:33 ` [bug#35518] guile-pfds hamts fix Jack Hill

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=878s29r4wv.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=35518-done@debbugs.gnu.org \
    --cc=amirouche@hyper.dev \
    --cc=rekado@elephly.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).