unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 15:42:09 +0200	[thread overview]
Message-ID: <83y4ejxiha.fsf@gnu.org> (raw)
In-Reply-To: <DUB109-W64929631B2C6661FCACC16842E0@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 14:26:41 +0100
> 
> > Instead, remove the Git repository, re-install Git as instructed in
> > nt/INSTALL, then re-clone the repository again.
> 
> Ok, I will do that. It surprises me that you need to tamper with the git
> system setting that affect all the projects using git, just for the sake
> of one project.

It's not for the sake of one project.  Installing Git as I indicated
is the only sensible thing for _any_ project.  For some reason, Git
for Windows doesn't have that as default; moreover, in the past I
remember some people arguing with me that what I suggest is actually
wrong (I disagree with their arguments).

I would encourage you to report this to the msysGit project as a bug.

> I am using git also for fmtcount and I have some changes
> pending, so I think that I will have to restore the original system
> settings when I come back to fmtcount. That is not a very practical
> solution.

The setting is on ~/.gitconfig and can be overridden by the
project-local .git/config file, if you need.  But my recommendation is
to switch all your Git-based projects to this default.  Otherwise, if
the project has files that need special EOL format, you will get in
trouble.

> I am quite novice with git, but just wondering whether it isn't possible
> to get the same effect with affecting emacs only by writing in the local
> config file (emacs/.git/config) some setting that would supersede the
> global and system settings, e.g. you would have
> 
> [core]
> autocrlf =
> 
> in the local config.

It's possible, yes.  Just make sure you have neither autocrlf nor eol
settings in your .git/config file, in the [core] section.

Once again, using anything else in other projects is just waiting for
trouble, so I really recommend this as a global setting.





  reply	other threads:[~2015-10-31 13:42 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 [this message]
2015-10-31 17:57           ` Vincent Belaïche
2015-10-31 18:21             ` Eli Zaretskii
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

  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=83y4ejxiha.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 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).