unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Fulbert <fulbert@bluewin.ch>
Cc: 47344@debbugs.gnu.org
Subject: [bug#47344] guix-cookbook : (Basic setup with mafinests)
Date: Tue, 23 Mar 2021 16:14:07 +0100	[thread overview]
Message-ID: <87v99h7vi8.fsf@nckx> (raw)
In-Reply-To: <YFn+6820/lIMD2+I@bluewin.ch>

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

Hi Fulbert,

Fulbert 写道:
> … with the patch this time !

Thanks!

Every time you send a new mail to bug-guix@gnu.org it will create 
a new bug number.  In this case you accidentally created two bug 
reports, [0] and [1].

No big deal, and I've merged them into one now, but make sure to 
send replies to an existing thread to the correct 
nnnnn@debbugs.gnu.org address.  If you CC bug-guix@ in addition to 
that, as some mail clients do by default, Debbugs will still know 
what you mean.

...and since you seem to be interested in submitting patches 
(yay!):

This also applies to multi-patch series: if you send 5 patches to 
bug-guix@ or guix-patches@, 5 separate issues will be created.  In 
that case, send a single cover letter to bug-guix/guix-patches@, 
wait for Debbugs to respond with the bug number, then send the 
actual patches to nnnnn@debbugs.gnu.org.

Kind regards,

T G-R

[0]: http://issues.guix.gnu.org/47343
[1]: http://issues.guix.gnu.org/47344

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

  reply	other threads:[~2021-03-23 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 14:44 [bug#47344] guix-cookbook : (Basic setup with mafinests) Fulbert
2021-03-23 15:14 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-03-23 18:20   ` Fulbert

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=87v99h7vi8.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=47344@debbugs.gnu.org \
    --cc=fulbert@bluewin.ch \
    --cc=me@tobias.gr \
    /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).