From: Eli Zaretskii <eliz@gnu.org>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: emacs-devel@gnu.org, phillip.lord@russet.org.uk
Subject: Re: Installing the current emacs-28 branch under Windows 10
Date: Tue, 12 Oct 2021 21:59:12 +0300 [thread overview]
Message-ID: <83czoaoyrj.fsf@gnu.org> (raw)
In-Reply-To: <86k0iiyvcs.fsf@duenenhof-wilhelm.de> (dieter@duenenhof-wilhelm.de)
> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
> Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org
> Date: Tue, 12 Oct 2021 20:02:43 +0200
>
> uidg1626@VSL7V7PW MINGW64 /d/Emacs/emacs (emacs-28)
> $ git config --list |grep crlf
> core.autocrlf=true
Bad idea: it should be 'false'. Git should not change the EOLs,
neither when it checks out files, nor when it pushes them upstream.
I'm not sure this is the root cause of your problem, but it might be.
Suggest to reconfigure Git, and then delete your local repository and
clone it again.
> Must be the default for this git installation on Windows, I didn't touch
> it.
When you install Git, it asks you how you want to treat EOLs, and you
should have selected "checkout as-is, checkin as-is" (or somesuch, I
don't remember the exact wording).
> A sample of text files are encoded in undecided-dos in the emacs
> repo. Do the files need to be encoded in Unix style line endings for
> MinGW tools?
Not for MinGW, for MSYS. The autotools you run are MSYS tools, and
MSYS is a fork of Cygwin; Cygwin tools expect Unix-style EOLs, yes.
They could definitely choke if they see Windows-style CRLF EOLs.
next prev parent reply other threads:[~2021-10-12 18:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:23 Installing the current emacs-28 branch under Windows 10 H. Dieter Wilhelm
2021-10-12 14:06 ` Eli Zaretskii
2021-10-12 18:02 ` H. Dieter Wilhelm
2021-10-12 18:59 ` Eli Zaretskii [this message]
2021-10-13 20:30 ` H. Dieter Wilhelm
2021-10-13 21:28 ` Óscar Fuentes
2021-10-14 6:45 ` Eli Zaretskii
2021-10-17 23:01 ` Óscar Fuentes
2021-10-17 23:43 ` Óscar Fuentes
2021-10-14 6:33 ` Eli Zaretskii
2021-10-14 15:59 ` H. Dieter Wilhelm
2021-10-14 16:41 ` Eli Zaretskii
2021-10-15 9:26 ` H. Dieter Wilhelm
2021-10-15 10:58 ` Eli Zaretskii
2021-10-16 9:57 ` H. Dieter Wilhelm
2021-10-18 20:13 ` H. Dieter Wilhelm
2021-10-18 20:34 ` Óscar Fuentes
2021-10-19 7:00 ` H. Dieter Wilhelm
2021-10-19 19:43 ` H. Dieter Wilhelm
2021-10-20 11:49 ` Eli Zaretskii
2021-10-20 19:15 ` H. Dieter Wilhelm
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=83czoaoyrj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dieter@duenenhof-wilhelm.de \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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).