From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: master 7555f93: Remove src/macuvs.h from Git repository
Date: Sat, 22 Jun 2019 10:35:40 +0300 [thread overview]
Message-ID: <83y31unkc3.fsf@gnu.org> (raw)
In-Reply-To: <a137b380-5011-2729-011f-8d7de46fa80f@cs.ucla.edu> (message from Paul Eggert on Fri, 21 Jun 2019 17:25:43 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 21 Jun 2019 17:25:43 -0700
> Cc: emacs-devel@gnu.org
>
> On 6/21/19 5:21 PM, Glenn Morris wrote:
> > Was having src/macuvs.h in the repository causing a problem?
> > It has changed twice since 2014.
>
> Not a major problem, no. I made the change because Lars ran into
> something; perhaps he can chime in.
So I think we should put it back, and we should this time have a
comment explaining why it is in Git although it's a generated file.
May I ask that you, Paul, will in the future not rush into changing
something, especially when we are not sure of its reasons, without
waiting a few days for possible comments from people who do know the
reasons? I think it will make the Git repository cleaner and will
prevent unnecessary discussions and arguments. TIA.
next prev parent reply other threads:[~2019-06-22 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190621220118.16051.70712@vcs0.savannah.gnu.org>
[not found] ` <20190621220121.8B68D209DE@vcs0.savannah.gnu.org>
2019-06-21 23:02 ` master 7555f93: Remove src/macuvs.h from Git repository Glenn Morris
2019-06-21 23:33 ` Paul Eggert
2019-06-22 0:21 ` Glenn Morris
2019-06-22 0:25 ` Paul Eggert
2019-06-22 7:35 ` Eli Zaretskii [this message]
2019-06-22 8:23 ` martin rudalics
2019-06-22 9:34 ` Eli Zaretskii
2019-06-22 10:20 ` Robert Pluim
2019-06-22 18:50 ` Paul Eggert
2019-06-22 19:21 ` Alan Third
2019-06-22 19:27 ` Paul Eggert
2019-06-22 8:56 ` Lars Ingebrigtsen
2019-06-22 20:56 ` Glenn Morris
2019-06-23 4:08 ` YAMAMOTO Mitsuharu
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=83y31unkc3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 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).