all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: help-guix@gnu.org, Lee Thompson <lee.p.thomp@gmail.com>,
	Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: Re: Help Sending Patch Series
Date: Fri, 01 Nov 2024 20:02:10 +0900	[thread overview]
Message-ID: <2DFDF18C-1D94-4B20-990D-D9196420104A@gmail.com> (raw)
In-Reply-To: <6724b3ff.050a0220.13b3.e39f@mx.google.com>

It should be guix-patches@gnu.org, not @debbugs.gnu.org

On November 1, 2024 7:57:02 PM GMT+09:00, Lee Thompson <lee.p.thomp@gmail.com> wrote:
>
>Ekaitz I've replied to you just a minute ago without CCing
>the mailing list, my apologies for the double reply.
>
>Ekaitz Zarraga <ekaitz@elenq.tech> writes:
>
>> The email should be sent to you pretty soon since your cover letter is
>> sent. Which address did you send your email to?
>I sent this to guix-patches@debbugs.gnu.org like so:
>```
>git send-email outgoing/0000-cover-letter.patch -a \
>    --to=guix-patches@debbugs.gnu.org \
>           $(etc/teams.scm cc mentors)
>```
>
>> Is this the first patch you send to Guix?
>Indeed
>
>> I don't know if that address is also moderated, it might be, si maybe
>> it's that?
>You could be right, I've just noticed this in the "Submitting Patches"
>info page:
>>    Expect some delay when you submit your very first patch to
>> <guix-patches@gnu.org>.  You have to wait until you get an
>> acknowledgement with the assigned tracking number.  Future
>> acknowledgements should not be delayed.
>

  reply	other threads:[~2024-11-01 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 10:09 Help Sending Patch Series Lee Thompson
2024-11-01 10:37 ` Ekaitz Zarraga
2024-11-01 10:57   ` Lee Thompson
2024-11-01 11:02     ` Maxim Cournoyer [this message]
2024-11-01 11:11       ` Lee Thompson

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=2DFDF18C-1D94-4B20-990D-D9196420104A@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=ekaitz@elenq.tech \
    --cc=help-guix@gnu.org \
    --cc=lee.p.thomp@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.
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.