From: changqi chen <ccq777@gmail.com>
To: "38389@debbugs.gnu.org" <38389@debbugs.gnu.org>
Subject: bug#38389: This issue fixed
Date: Tue, 26 Nov 2019 14:47:25 -0500 [thread overview]
Message-ID: <26434b72-a963-4f6f-b482-1b014a77f792@Spark> (raw)
In-Reply-To: <cfd85d5b-e8f0-422d-8a72-a7fa052c4236@Spark>
[-- Attachment #1: Type: text/plain, Size: 51 bytes --]
I figured it out. This issue can close. Thank you!
[-- Attachment #2: Type: text/html, Size: 226 bytes --]
prev parent reply other threads:[~2019-11-26 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00e41933-0807-4ac9-84f0-6dbcdc816429@Spark>
2019-11-26 15:59 ` bug#38389: Emacs HEAD code build failed because cannot find tputs changqi chen
2019-11-26 16:35 ` bug#38389: I figure out changqi chen
2019-11-26 16:41 ` bug#38389: Emacs HEAD code build failed because cannot find tputs Lars Ingebrigtsen
2019-11-26 16:46 ` changqi chen
2019-11-26 19:47 ` changqi chen [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://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=26434b72-a963-4f6f-b482-1b014a77f792@Spark \
--to=ccq777@gmail.com \
--cc=38389@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/emacs.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).