From: "Perry E. Metzger" <perry@piermont.com>
To: emacs-devel@gnu.org
Subject: build modifies config.guess and config.sub
Date: Wed, 28 Jul 2021 16:17:27 -0400 [thread overview]
Message-ID: <6af8fd02-e9ef-f0f6-8ebc-70051f4b4d02@piermont.com> (raw)
Howdy, all!
Whenever I do a "git status" after cleaning up after a build, I learn
that the files
build-aux/config.guess
build-aux/config.sub
have been modified. It's easy enough to do a "git restore" on them, but
should they should actually be checked in? I thought they were supplied
by the autotools?
Perry
next reply other threads:[~2021-07-28 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 20:17 Perry E. Metzger [this message]
2021-07-28 20:27 ` build modifies config.guess and config.sub Philipp
2021-07-29 6:06 ` Eli Zaretskii
2021-07-29 23:11 ` Perry E. Metzger
2021-07-30 6:03 ` Eli Zaretskii
2021-07-30 13:48 ` Perry E. Metzger
2021-07-30 13:54 ` Eli Zaretskii
2021-07-30 18:35 ` Alan Third
2021-07-30 18:53 ` Eli Zaretskii
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=6af8fd02-e9ef-f0f6-8ebc-70051f4b4d02@piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@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).