unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 32689@debbugs.gnu.org
Subject: [bug#32689] control message for bug #32689
Date: Sat, 27 Oct 2018 16:38:29 +0200	[thread overview]
Message-ID: <87bm7fa1zu.fsf@gnu.org> (raw)
In-Reply-To: <165d3e13c38.6a6b1c06974273209.-184459513028708500@zoho.com> (Ricardo Wurmus's message of "Thu, 13 Sep 2018 19:01:15 +0200")

Hello!

Ricardo Wurmus <rekado@elephly.net> skribis:

> owner 32689 !

Are you taking care of these two patches?  :-)

Thanks,
Ludo’.

       reply	other threads:[~2018-10-27 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <165d3e13c38.6a6b1c06974273209.-184459513028708500@zoho.com>
2018-10-27 14:38 ` Ludovic Courtès [this message]
2018-10-27 16:55   ` bug#32689: control message for bug #32689 Ricardo Wurmus
2018-10-28 22:33     ` [bug#32689] " Ludovic Courtès

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=87bm7fa1zu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32689@debbugs.gnu.org \
    --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).