unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "Jihyun Cho" <jihyun.jo@gmail.com>
Cc: emacs-devel Mailinglist <emacs-devel@gnu.org>
Subject: Re: [PATCH] array index bug in 'hangul.el'
Date: Mon, 11 Aug 2008 11:13:34 +0200	[thread overview]
Message-ID: <87profx6bl.fsf@ambire.localdomain> (raw)
In-Reply-To: <9d644d9b0808101815o15a7703l533e8e45871696b@mail.gmail.com> (Jihyun Cho's message of "Mon, 11 Aug 2008 10:15:55 +0900")

() "Jihyun Cho" <jihyun.jo@gmail.com>
() Mon, 11 Aug 2008 10:15:55 +0900

   Ok. I see.
   When you type the Korean Jongseong, bug occurs.
   So you can not type some characters in the Korean 3-Bulsik.
   I fixed it.

Juanma is asking for a specific form of explanation, one that can
be prepended to the ChangeLog file.  In this case, it is best if
you respond like so:

|Here's a suitable ChangeLog entry:
|
|YYYY-MM-DD  Jihyun Cho  <jihyun.jo@gmail.com>  (tiny change)
|
|	* quail/hangul.el (hangul3-input-method-jong): Fix typo.

The asterisk, parens and colon are part of the ChangeLog format.
The filename is relative to the closest directory (traveling towards
the root) that contains a ChangeLog file.  The parenthesized symbol
indicates the top-level form where the change occurs.  The blurb
"Fix typo" describes the change.

In this way, you show good spirit by playing the maintainer's role.

thi




  reply	other threads:[~2008-08-11  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10  6:02 [PATCH] array index bug in 'hangul.el' Jihyun Cho
2008-08-10 11:53 ` Juanma Barranquero
2008-08-11  0:29   ` Jihyun Cho
2008-08-11  0:31     ` Juanma Barranquero
2008-08-11  1:15       ` Jihyun Cho
2008-08-11  9:13         ` Thien-Thi Nguyen [this message]
2008-08-11 15:11           ` Jihyun Cho
2008-08-11 15:22             ` Lennart Borgman (gmail)
2008-08-11 18:08               ` Thien-Thi Nguyen
2008-08-11  0:55     ` Kenichi Handa
2008-08-10 23:59 ` Kenichi Handa

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=87profx6bl.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=emacs-devel@gnu.org \
    --cc=jihyun.jo@gmail.com \
    /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).