unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Vollmert <rob@vllmrt.net>
To: 36661@debbugs.gnu.org
Subject: [bug#36661] bump
Date: Mon, 22 Jul 2019 22:03:28 +0200	[thread overview]
Message-ID: <84C9E62E-1F7E-463B-8702-2A20203B6223@vllmrt.net> (raw)
In-Reply-To: <20190715105915.23913-1-rob@vllmrt.net>

Hi,

would someone be so kind as to apply this? It’s a bit of a pain
having to rebase it over test file additions.

(If you’re worried about the backslashes being non-aligned: Note
that this appears so in the patch for module names of lengths
3, 11, ….)

Robert

  parent reply	other threads:[~2019-07-22 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 10:59 [bug#36661] [PATCH] tests: Sort scheme tests alphabetically Robert Vollmert
2019-07-15 12:01 ` Efraim Flashner
2019-07-15 13:00   ` Robert Vollmert
2019-07-22 20:03 ` Robert Vollmert [this message]
2019-07-23  6:57   ` bug#36661: bump Efraim Flashner

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=84C9E62E-1F7E-463B-8702-2A20203B6223@vllmrt.net \
    --to=rob@vllmrt.net \
    --cc=36661@debbugs.gnu.org \
    /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).