From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Source code, git and cvs
Date: Thu, 20 Jul 2023 16:05:22 +0000 [thread overview]
Message-ID: <dHnJYwNL8fGKs1tMfuNfEdP2dAmLy23fI9306UvbyQHv2szb5V0KRA0rKtg8uv1D6MOP3TWRKMg--FdewKQQqoKoaK4RRl8PVTJ9Ez5qGCM=@proton.me> (raw)
In-Reply-To: <83ilae3899.fsf@gnu.org>
Sent with Proton Mail secure email.
------- Original Message -------
On Friday, July 21st, 2023 at 3:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 20 Jul 2023 15:09:44 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> >
> > > INSTALL is for building a release tarball. INSTALL.REPO is for
> > > building a clone of the repository. They are different because some
> > > files are present in the tarball, but not in the repository (they are
> > > generated during the build from the repository).
> >
> > Can this detail be included in README ? Because currently README only
> > describes INSTALL.
>
>
> INSTALL itself already includes that information:
>
> For information about building from a Git checkout (rather than an
> Emacs release), read the INSTALL.REPO file first.
The README says
"The file INSTALL in this directory says how to build and install GNU
Emacs on various systems, once you have unpacked or checked out the
entire Emacs file tree."
The above is incomplete and users are given just one aspect.
Instead README should explain that there are two installation mechanisms,
using a "Release Tarball" or using a "Snapshot Repository".
The file INSTALL describes how to build and install emacs from a tarball, whilst INSTALL-REPO
explains how to build and install using a repository.
Easy, to the point, and the information is provided instantly.
prev parent reply other threads:[~2023-07-20 16:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:01 Source code, git and cvs uzibalqa
2023-07-20 13:38 ` Po Lu
2023-07-20 13:58 ` uzibalqa
2023-07-20 14:23 ` Eli Zaretskii
2023-07-20 15:09 ` uzibalqa
2023-07-20 15:34 ` Robert Pluim
2023-07-20 15:36 ` Eli Zaretskii
2023-07-20 15:47 ` uzibalqa
2023-07-20 16:35 ` Eli Zaretskii
2023-07-20 17:33 ` uzibalqa
2023-07-20 18:31 ` Eli Zaretskii
2023-07-20 19:12 ` uzibalqa
2023-07-20 20:10 ` uzibalqa
2023-07-21 5:22 ` Eli Zaretskii
2023-07-21 6:12 ` Po Lu
2023-07-21 10:43 ` uzibalqa
2023-07-21 10:59 ` uzibalqa
2023-07-21 11:18 ` uzibalqa
2023-07-21 12:30 ` Eli Zaretskii
2023-07-21 12:40 ` uzibalqa
2023-07-21 12:51 ` Eli Zaretskii
2023-07-21 4:27 ` tomas
2023-07-21 10:35 ` uzibalqa
2023-07-21 12:12 ` Po Lu
2023-07-21 12:52 ` uzibalqa
2023-07-21 14:20 ` [External] : " Drew Adams
2023-07-21 15:30 ` uzibalqa
2023-07-20 16:05 ` uzibalqa [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='dHnJYwNL8fGKs1tMfuNfEdP2dAmLy23fI9306UvbyQHv2szb5V0KRA0rKtg8uv1D6MOP3TWRKMg--FdewKQQqoKoaK4RRl8PVTJ9Ez5qGCM=@proton.me' \
--to=uzibalqa@proton.me \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).