unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Chong Yidong <cyd@stupidchicken.com>
Subject: bug#3428: marked as done (23.0.94; Missing source files?)
Date: Thu, 04 Jun 2009 01:35:06 +0000	[thread overview]
Message-ID: <handler.3428.D3428.124407903018117.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 200905311131.n4VBVf24005498@sonorant.lingfil.uu.se

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]


Your message dated Wed, 03 Jun 2009 21:30:27 -0400
with message-id <87vdncn5u4.fsf@cyd.mit.edu>
and subject line Re: bug#3428: 23.0.94; Missing source files?
has caused the Emacs bug report #3428,
regarding 23.0.94; Missing source files?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3428: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3428
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 2663 bytes --]

From: "Per Starbäck" <per@starback.se>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.94; Missing source files?
Date: Sun, 31 May 2009 13:31:41 +0200
Message-ID: <200905311131.n4VBVf24005498@sonorant.lingfil.uu.se>

In GNU Emacs 23.0.94:

There are several files in emacs-23.0.94/lisp/international
that are automatically generated from files that aren't in the Emacs
distribution. Is that an oversight? At least

  charprop.el, eucjp-ms.el, uni-name.el and uni-old-name.el

have comments about being automatically generated from such files.
The files I'm missing are 

  unidata-gen.el, eucJP-13th.txt, eucJP-udc.txt, eucJP-ibmext.txt
  and UnicodeData.txt

judging by those comments.


[-- Attachment #3: Type: message/rfc822, Size: 1664 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: 3428-done@emacsbugs.donarmstrong.com, per@starback.se
Subject: Re: bug#3428: 23.0.94; Missing source files?
Date: Wed, 03 Jun 2009 21:30:27 -0400
Message-ID: <87vdncn5u4.fsf@cyd.mit.edu>

Richard Stallman <rms@gnu.org> writes:

> This looks good, but this
>
>     which is not included in the Emacs distribution; it can be found in
>     the admin/unidata directory of the Emacs source repository.
>
> should say precisely WHERE the Emacs source repository is.

OK, done.

      reply	other threads:[~2009-06-04  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vdncn5u4.fsf@cyd.mit.edu>
2009-05-31 11:31 ` bug#3428: 23.0.94; Missing source files? Per Starbäck 
2009-06-04  1:35   ` Emacs bug Tracking System [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=handler.3428.D3428.124407903018117.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.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).