From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: 良ϖ <p.de.boisset@gmail.com>
Cc: Emacs Help <help-gnu-emacs@gnu.org>, pierre@2bst.fr
Subject: Re: Build failure caused by a .tit file
Date: Mon, 17 Apr 2017 18:57:01 +0300 [thread overview]
Message-ID: <87h91nauya.fsf@gkayaalp.com> (raw)
In-Reply-To: <CA+cPLChaWQVdZSYA+BNKJK9vq+h6bNziftF5GVR=RbtJd7ibKA@mail.gmail.com> ("良ϖ"'s message of "Mon, 17 Apr 2017 14:41:39 +0000")
On 2017-04-17 14:41 GMT, 良ϖ <p.de.boisset@gmail.com> wrote:
> Well, have you tried to figure out if it's a big tit file?
It has 565 lines and ~10000 characters.
next prev parent reply other threads:[~2017-04-17 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 14:03 Build failure caused by a .tit file Göktuğ Kayaalp
2017-04-17 14:41 ` 良ϖ
2017-04-17 15:57 ` Göktuğ Kayaalp [this message]
2017-04-17 14:45 ` Eli Zaretskii
2017-04-17 15:55 ` Göktuğ Kayaalp
2017-04-17 16:21 ` Eli Zaretskii
2017-04-17 23:08 ` Göktuğ Kayaalp
2017-04-18 2:43 ` Eli Zaretskii
2017-04-18 12:41 ` Göktuğ Kayaalp
2017-04-18 13:16 ` Göktuğ Kayaalp
2017-04-18 15:02 ` Eli Zaretskii
2017-04-18 14:56 ` Eli Zaretskii
2017-04-18 16:19 ` Göktuğ Kayaalp
2017-04-18 16:39 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h91nauya.fsf@gkayaalp.com \
--to=self@gkayaalp.com \
--cc=help-gnu-emacs@gnu.org \
--cc=p.de.boisset@gmail.com \
--cc=pierre@2bst.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).