From: Leo Famulari <leo@famulari.name>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 25258-done@debbugs.gnu.org
Subject: bug#25258: Bashisms when building 0.11.0
Date: Sun, 22 Mar 2020 16:28:32 -0400 [thread overview]
Message-ID: <20200322202832.GA18995@jasmine.lan> (raw)
In-Reply-To: <20190213014630.GA27743@jasmine.lan>
On Tue, Feb 12, 2019 at 08:46:30PM -0500, Leo Famulari wrote:
> About two years have passed on this bug report without comment. Is it a
> "wontfix"?
Based on the lack of interest I've closed this bug.
next prev parent reply other threads:[~2020-03-22 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 7:26 bug#25258: Bashisms when building 0.11.0 pelzflorian (Florian Pelz)
2019-02-13 1:46 ` Leo Famulari
2020-03-22 20:28 ` Leo Famulari [this message]
2020-05-16 6:33 ` bug#25258: Bashisms in make rules elaexuotee--- via Bug reports for GNU Guix
2020-05-17 16:42 ` Vincent Legoll
2020-05-17 17:34 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=20200322202832.GA18995@jasmine.lan \
--to=leo@famulari.name \
--cc=25258-done@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).