From: zimoun <zimon.toutoune@gmail.com>
To: Alex <aleksq@protonmail.ch>
Cc: Softwafe Engineer <timsofteng@gmail.com>,
46580-done@debbugs.gnu.org,
Alexandru-Sergiu Marton <brown121407@posteo.ro>
Subject: bug#46580: vim-full fails to build
Date: Sat, 06 Mar 2021 01:33:35 +0100 [thread overview]
Message-ID: <867dmlruhs.fsf@gmail.com> (raw)
In-Reply-To: <86lfb1s8ki.fsf@gmail.com>
On Fri, 05 Mar 2021 at 20:29, zimoun <zimon.toutoune@gmail.com> wrote:
> Hi again,
>
> Fix with patch: <http://issues.guix.gnu.org/issue/46950>.
Patch pushed as c8cbd369eb512b0bc5cc0d5dfc2b5d35da50aa4f.
Thanks for the report.
Cheers,
simon
prev parent reply other threads:[~2021-03-06 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 23:49 bug#46580: vim-full fails to build Alex via Bug reports for GNU Guix
2021-02-24 8:46 ` Alexandru-Sergiu Marton
2021-02-24 18:25 ` zimoun
2021-03-05 18:30 ` zimoun
2021-03-05 19:29 ` zimoun
2021-03-06 0:33 ` zimoun [this message]
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=867dmlruhs.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=46580-done@debbugs.gnu.org \
--cc=aleksq@protonmail.ch \
--cc=brown121407@posteo.ro \
--cc=timsofteng@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 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).