unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: root@worik.org, 53627-done@debbugs.gnu.org
Subject: bug#53627: 29.0.50; Incorrect installation instructions
Date: Sun, 30 Jan 2022 08:27:25 +0200	[thread overview]
Message-ID: <83czk9buwi.fsf@gnu.org> (raw)
In-Reply-To: <xm46v8y2tcy5.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de)

> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
> Date: Sat, 29 Jan 2022 23:05:38 +0100
> Cc: 53627@debbugs.gnu.org
> 
> >> Please read INSTALL.REPO in the same directory, it says
> >
> > I can cope.  I did not need that file.   I was not asking for help.  I
> > was reporting a bug.
> 
> I'm not sure that this is a bug because in INSTALL it says:
> 
>   This file contains general information on building GNU Emacs.
>   For more information specific to the MS-Windows, GNUstep/macOS, and
>   MS-DOS ports, also read the files nt/INSTALL, nextstep/INSTALL, and
>   msdos/INSTALL.  For information about building from a repository checkout
>   (rather than a release), also read the file INSTALL.REPO.
> 
> 
> Thus INSTALL is for installing from a release source archive and
> INSTALL.REPO is for installing Emacs from a source repository.

Indeed, and so I don't think there's a bug here, and I'm closing this
bug report.





  reply	other threads:[~2022-01-30  6:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 21:39 bug#53627: 29.0.50; Incorrect installation instructions worik
2022-01-29 21:48 ` H. Dieter Wilhelm
2022-01-29 21:52   ` worik
2022-01-29 22:05     ` H. Dieter Wilhelm
2022-01-30  6:27       ` Eli Zaretskii [this message]
2022-01-30  1:50     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-30 22:54       ` Benjamin Riefenstahl
2022-01-31 15:25         ` Lars Ingebrigtsen

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=83czk9buwi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53627-done@debbugs.gnu.org \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=root@worik.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).