From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: ding@gnus.org
Subject: Re: git gnus info compilation fails in cygwin
Date: Mon, 10 Feb 2014 18:02:58 +0530 [thread overview]
Message-ID: <87d2ivuozp.fsf@gmail.com> (raw)
In-Reply-To: <b4ma9dzxyzu.fsf@jpl.org>
On Mon, Feb 10 2014,Katsumi Yamaoka wrote:
> Katsumi Yamaoka wrote:
>> Besides this, I've installed some fixes so that the Git Gnus can
>> be compiled even if the makeinfo command is not available. So,
>> try downloading it again anyway.
>
> Please check it out again if you've done it before seeing this
> message. I've fixed it again so as to work for the no-makeinfo
> case.
>
>
There was some problem with the permission bits of the file. I did a
chmod 755 and it compiled without issues. Though it never had an
issue over the last couple of months since using git gnus.
sivaram
--
prev parent reply other threads:[~2014-02-10 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 1:58 Sivaram Neelakantan
2014-02-10 3:59 ` Katsumi Yamaoka
2014-02-10 6:28 ` Katsumi Yamaoka
2014-02-10 12:32 ` Sivaram Neelakantan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2ivuozp.fsf@gmail.com \
--to=nsivaram.net@gmail.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).