all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: a.s@realize.ch, emacs-devel@gnu.org
Subject: Re: Minor doc improvement in nt/INSTALL.W64
Date: Thu, 29 Sep 2016 12:17:59 +0300	[thread overview]
Message-ID: <426b32b4-a8e4-54ce-dae0-8007c22824ab@gmail.com> (raw)
In-Reply-To: <83twdbhmey.fsf@gnu.org>

Since we're talking about Windows here, forcing people to use somewhat 
new version of git there is not that bad. That said, I don't think that 
those commands(config, rm and reset) work differently even in much older 
versions of git. If they do, it's a bug in those versions.

Automatic line ending conversions by default is really a great feature 
of git. For comparison, in hg you have to explicitly enable an extension 
for that. Then, when you enabled that extension, those people who did 
not, can still commit to your repo and screw your line endings. So, the 
problem case here - someone builds Emacs, touches his global gitconfig, 
then commits to some other project and screws up line endings there. 
It's not something that's "really wrong", just moderately, but fixing 
instructions is pretty easy.

Due to those reasons, I believe if we want to suggest one way of doing 
things, config-rm-reset is the one we want to use. But again, it's your 
call.

-- 
Best Regards,
Nikolay Kudryavtsev




      reply	other threads:[~2016-09-29  9:17 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
2016-09-19 11:06     ` Nikolay Kudryavtsev
2016-09-19 16:41   ` Eli Zaretskii
2016-09-29  9:17     ` Nikolay Kudryavtsev [this message]

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=426b32b4-a8e4-54ce-dae0-8007c22824ab@gmail.com \
    --to=nikolay.kudryavtsev@gmail.com \
    --cc=a.s@realize.ch \
    --cc=eliz@gnu.org \
    --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 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.