From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: 21789@debbugs.gnu.org
Subject: bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration)
Date: Sat, 31 Oct 2015 20:21:11 +0200 [thread overview]
Message-ID: <83wpu2yk4o.fsf@gnu.org> (raw)
In-Reply-To: <DUB109-W5819EE3498F44FC04DDEE8842E0@phx.gbl>
> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> CC: "21789@debbugs.gnu.org" <21789@debbugs.gnu.org>
> Date: Sat, 31 Oct 2015 18:57:37 +0100
>
> So, to get to the point, removing the core.autocrlf and suchlikes from
> the config is probably a good thing, but IMHO that is not enough,
> setting file eol attributes with discriminating wildcard should also be
> done.
No, you don't need anything except removing all of these settings.
The defaults are exactly what you want, when these settings are
absent.
> git config --system --unset core.autocrlf cd /path/to/project/fmtcount
> git config --local --bool -add core.autocrlf true cd
> /path/to/project/emacs git config --local --bool -add core.autocrlf
> false
>
> The two last instructions are probably useless, but I made it so that in
> the future people on MSW wanting to build Emacs from source with msysGit
> won't fail like me.
The last one is not needed.
> I have now the following setting in the .git/config [core] section
>
> autocrlf = false
I don't have it, and never felt the need.
next prev parent reply other threads:[~2015-10-31 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:53 bug#21789: 25.0.50; Can' build Emacs (my first build since GIT migration) Vincent Belaïche
2015-10-30 13:49 ` Eli Zaretskii
2015-10-30 18:17 ` Vincent Belaïche
2015-10-30 20:31 ` Eli Zaretskii
2015-10-31 13:26 ` Vincent Belaïche
2015-10-31 13:42 ` Eli Zaretskii
2015-10-31 17:57 ` Vincent Belaïche
2015-10-31 18:21 ` Eli Zaretskii [this message]
2015-10-30 18:42 ` Glenn Morris
2015-10-30 20:33 ` Eli Zaretskii
2015-10-30 20:41 ` Vincent Belaïche
2015-10-30 22:27 ` Vincent Belaïche
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=83wpu2yk4o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21789@debbugs.gnu.org \
--cc=vincent.b.1@hotmail.fr \
/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.