unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alain Schneble <a.s@realize.ch>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Minor doc improvement in nt/INSTALL.W64
Date: Mon, 19 Sep 2016 08:33:53 +0200	[thread overview]
Message-ID: <86bmzkiejy.fsf@realize.ch> (raw)
In-Reply-To: <90f7882c-ec7d-fd71-cb87-b5c281f7e834@gmail.com> (Nikolay Kudryavtsev's message of "Mon, 19 Sep 2016 04:47:27 +0300")

Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:

> I think you can just clone the repo and do:
>
> git config core.eol false
> git config core.safecrlf false
> git config core.autocrlf false
> git rm --cached -r .
> git reset --hard
>
> I tried repeating the issue, autogen.sh breaks on normal clone, this
> fixes it like the current procedure, but this does not require cloning
> again and does not touch the global git config.

FWIW, `git clone --config ...' doesn't touch global git config either.
This should be mentioned before a procedure like you propose, I think.
That's what I tried to document with the patch in my previous message:
https://lists.gnu.org/archive/html/emacs-devel/2016-08/msg00416.html.

I'm not even sure if the procedure of "how to fix an already checked out
repository" should be part of this document.

Maybe `git clone --config ...' should be the preferred choice over the
option of altering the global git config?

Alain




  reply	other threads:[~2016-09-19  6:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 19:34 Minor doc improvement in nt/INSTALL.W64 Alain Schneble
2016-09-19  1:47 ` Nikolay Kudryavtsev
2016-09-19  6:33   ` Alain Schneble [this message]
2016-09-19 11:06     ` Nikolay Kudryavtsev
2016-09-19 16:41   ` Eli Zaretskii
2016-09-29  9:17     ` Nikolay Kudryavtsev

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=86bmzkiejy.fsf@realize.ch \
    --to=a.s@realize.ch \
    --cc=emacs-devel@gnu.org \
    --cc=nikolay.kudryavtsev@gmail.com \
    /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).