unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Jonas Hahnfeld <hahnjo@hahnjo.de>,  guile-devel@gnu.org
Subject: Re: [PATCH] Fixes for custom-ports
Date: Sat, 10 Feb 2024 11:08:09 +0100	[thread overview]
Message-ID: <875xywk4xi.fsf@gnu.org> (raw)
In-Reply-To: <87fry2p7ku.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 08 Feb 2024 23:47:29 -0500")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

>> PS: As far as I’m concerned, patches sent to bug-guile@gnu.org are less
>>     likely to be lost because I see them in M-x debbugs.
>>
>
> The contributing documentation mention to send patches to
> guile-devel at gnu dot org; should this guidance be changed?
>
> From the HACKING file:
>
> - If you have put together a change that meets the coding standards
> described below, we encourage you to submit it to Guile.  Post your
> patch to guile-devel@gnu.org.

Good idea; I’ve expanded that part, I hope it’s fine for everyone.

Thanks,
Ludo’.



  reply	other threads:[~2024-02-10 10:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29  9:51 [PATCH] Fixes for custom-ports Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2023-11-28 21:01 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-01-04 10:36   ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2023-11-28 21:11 ` Jean Abou Samra
2023-11-29  6:47   ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2023-11-29  6:54     ` Jean Abou Samra
2023-11-29  7:26       ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-01-29 13:46 ` Ludovic Courtès
2024-01-29 21:34   ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-02-09  4:47   ` Maxim Cournoyer
2024-02-10 10:08     ` Ludovic Courtès [this message]
2024-02-11 16:41       ` Maxim Cournoyer

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=875xywk4xi.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=hahnjo@hahnjo.de \
    --cc=maxim.cournoyer@gmail.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. 
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).