all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 14757@debbugs.gnu.org
Subject: bug#14757: 24.3.50; cannot find README.W32 in MS Windows builds
Date: Sun, 30 Jun 2013 11:32:06 -0700 (PDT)	[thread overview]
Message-ID: <cf60c929-3316-4973-9471-16dfbcd034ec@default> (raw)

I cannot find the file README.W32 in the MS Windows development binaries
distributed here:
https://www.dropbox.com/sh/zmxzw7pk2ml7qip/jS1Fuz1pZr
or here:
https://www.dropbox.com/sh/3pgcb3iiy8s9irl/c171Xhsd99

Dunno whether this is a problem generally or just with such builds.

According to info Eli sent me, the file exists in the repository but it
does not get copied into the installation tree, and that is a bug.


In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-06-27 on ODIEONE
Bzr revision: 113205 dgutov@yandex.ru-20130627095155-f1lv1c7xf99g1sss
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 CFLAGS=-O0 -g3 LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'





             reply	other threads:[~2013-06-30 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 18:32 Drew Adams [this message]
2013-06-30 20:11 ` bug#14757: 24.3.50; cannot find README.W32 in MS Windows builds Juanma Barranquero
2013-07-01  2:43   ` Eli Zaretskii
2013-07-01  3:08     ` Juanma Barranquero
2014-02-08  6:37       ` Lars Ingebrigtsen
2014-02-08  9:35         ` Eli Zaretskii
2014-02-08 10:26           ` Juanma Barranquero
2014-02-08 10:57             ` Eli Zaretskii
2014-02-10 17:49               ` Juanma Barranquero
2014-02-10 18:16                 ` Eli Zaretskii
2014-02-13  3:21                   ` Juanma Barranquero

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cf60c929-3316-4973-9471-16dfbcd034ec@default \
    --to=drew.adams@oracle.com \
    --cc=14757@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.