unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: John Kehayias <john.kehayias@protonmail.com>, guix-devel@gnu.org
Subject: Re: Create branch for Haskell build changes and updates?
Date: Sat, 24 Jul 2021 17:00:13 +0200	[thread overview]
Message-ID: <87bl6r4v0i.fsf@elephly.net> (raw)
In-Reply-To: <87czr73k4e.fsf@yoctocell.xyz>


Xinglu Chen <public@yoctocell.xyz> writes:

> Sending it
> to guix-patches would make it more likely to be forgotten since 
> it
> is a higher-volume list.

The opposite.  guix-patches is backed by debbugs / 
issues.guix.gnu.org, so we can query it and show forgotten 
patches.  Sending patches to guix-devel is how things get lost.

> Now that more people have showed interest, I recently sent a 
> patch for
> it to guix-patches[1].  I still have to address some failing 
> tests
> before it’s ready to merge.  :)
>
> [1]: https://issues.guix.gnu.org/49606

Thanks.

-- 
Ricardo


      reply	other threads:[~2021-07-24 15:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 17:24 Create branch for Haskell build changes and updates? John Kehayias
2021-07-07  5:47 ` Xinglu Chen
2021-07-07 14:47   ` John Kehayias
2021-07-07 15:02     ` John Soo
2021-07-08 17:45     ` Xinglu Chen
2021-07-09 14:06       ` Ricardo Wurmus
2021-07-09 15:21         ` John Kehayias
2021-07-09 16:44           ` Ricardo Wurmus
2021-07-09 18:45             ` John Kehayias
2021-07-10 15:39           ` Xinglu Chen
2021-07-20 11:58             ` Philip Munksgaard
2021-07-20 16:49               ` Ricardo Wurmus
2021-07-20 19:41                 ` Philip Munksgaard
2021-07-21 21:10                 ` Ricardo Wurmus
2021-07-27 21:24                   ` John Kehayias
2021-07-27 21:34                     ` Ricardo Wurmus
2021-07-20 22:24   ` Ricardo Wurmus
2021-07-24 13:40     ` Xinglu Chen
2021-07-24 15:00       ` Ricardo Wurmus [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=87bl6r4v0i.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=public@yoctocell.xyz \
    /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).