all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 15:47:32 +0000	[thread overview]
Message-ID: <bYsUoZG5dIHnr2snbMmYi6V3GVlVMdHkv9cKiAd2Nbut-_0GBaAPsH9zhxSBtEodki2KLenF74vFfGQr-hZkr9QcMN-DjzpWSWNvBh-hlNU=@proton.me> (raw)
In-Reply-To: <83ilae3899.fsf@gnu.org>

------- 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.

I do not like the idea that information is stored deeper and deeper
in hierarchy.  They are two separate things and should be mentioned 
in the README.  Not having to read about where to find information 
about installing from the repo using the file intended to show how 
to install from the tarball.

Do not make it difficult for users to get to the basic information 
they need.

README should describe both immediately at the start.  Not just about
installing from the tarball.



  reply	other threads:[~2023-07-20 15:47 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 [this message]
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

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='bYsUoZG5dIHnr2snbMmYi6V3GVlVMdHkv9cKiAd2Nbut-_0GBaAPsH9zhxSBtEodki2KLenF74vFfGQr-hZkr9QcMN-DjzpWSWNvBh-hlNU=@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.
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.