From: Juri Linkov <juri@jurta.org>
Cc: walters@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [juri@jurta.org: Why 10 lines?]
Date: Fri, 02 Jun 2006 12:28:59 +0300 [thread overview]
Message-ID: <87k67zlxqi.fsf@jurta.org> (raw)
In-Reply-To: <E1Fm0jz-0004BJ-00@etlken> (Kenichi Handa's message of "Fri, 02 Jun 2006 12:54:27 +0900")
> I think the change is good and has no problem. So, I installed it.
Thanks. What do you think about a related uninstalled change in
http://lists.gnu.org/archive/html/emacs-devel/2005-10/msg00916.html.
Do you see any problems with it?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2006-06-02 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Fm05r-0002bd-6s@fencepost.gnu.org>
2006-06-02 3:54 ` [juri@jurta.org: Why 10 lines?] Kenichi Handa
2006-06-02 9:28 ` Juri Linkov [this message]
2006-06-02 11:19 ` Kenichi Handa
2006-06-02 22:21 ` Kevin Rodgers
2006-06-03 6:43 ` Juri Linkov
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=87k67zlxqi.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=walters@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).