From: Alexandru-Sergiu Marton <brown121407@posteo.ro>
To: 46642@debbugs.gnu.org
Subject: bug#46642: vim-full broken
Date: Sat, 27 Feb 2021 19:10:47 +0200 [thread overview]
Message-ID: <87zgzpe8rs.fsf@posteo.ro> (raw)
In-Reply-To: <CAP7bFfCc_mWqY4Qi=2-eBXU8NJFmT-JvKwW6Msd0OW_VsqadjQ@mail.gmail.com>
Hello,
The commit Simon pointed out does indeed look like the culprit. I tried
building it myself vim-full with the time machine and it works before
988ac06ce8cf9b1760094e0e2ff23960355d07eb but any random commit I pick
after it (including it) makes the build fail.
--
Alexandru-Sergiu Marton
prev parent reply other threads:[~2021-02-27 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 18:43 bug#46642: Softwafe Engineer
2021-02-24 17:36 ` bug#46642: vim-full broken zimoun
2021-02-27 17:10 ` Alexandru-Sergiu Marton [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=87zgzpe8rs.fsf@posteo.ro \
--to=brown121407@posteo.ro \
--cc=46642@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).