From: Tino Calancha <tino.calancha@gmail.com>
To: 24605-done@debbugs.gnu.org
Subject: bug#24605: Subject: 25.1.50; form-at-point might fail for some THINGS
Date: Tue, 11 Oct 2016 11:53:48 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610111152090.2746@calancha-pc> (raw)
In-Reply-To: <alpine.DEB.2.20.1610041521480.19326@calancha-pc>
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> Looks good to me.
Pushed fix to master as commit 9640e9f4
prev parent reply other threads:[~2016-10-11 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 6:22 bug#24605: Subject: 25.1.50; form-at-point might fail for some THINGS Tino Calancha
2016-10-05 1:15 ` npostavs
2016-10-05 3:35 ` Tino Calancha
2016-10-05 11:50 ` Noam Postavsky
2016-10-05 12:30 ` Tino Calancha
2016-10-05 12:38 ` Tino Calancha
2016-10-05 13:09 ` Eli Zaretskii
2016-10-05 13:52 ` Tino Calancha
2016-10-05 15:59 ` Eli Zaretskii
2016-10-06 7:13 ` Andreas Röhler
2016-10-11 2:53 ` Tino Calancha [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=alpine.DEB.2.20.1610111152090.2746@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=24605-done@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).