From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Recommend these .gitconfig settings for git integrity.
Date: Mon, 01 Feb 2016 21:34:15 +0100 [thread overview]
Message-ID: <8737tci308.fsf@wanadoo.es> (raw)
In-Reply-To: 56AF9899.7050800@cs.ucla.edu
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 02/01/2016 08:51 AM, Óscar Fuentes wrote:
>> I would prefer a `make' target or script
>
> It is already in a script,
Oh, please...
> and the script plainly notifies developers
> of the changes it makes to files under ./.git.
That's a good thing, but still not enough. For starters, if I edit
.git/config, next time autogen.sh is run it will revert the edits,
right? The script I use for building Emacs contains
git clean -f -d -x
./autogen.sh
... to ensure that the build is not tainted by previous builds.
How about mentioning (not applying) the recommended settings on
autogen.sh, with instructions for running a script that makes the
changes? That ensures that the user is aware of the changes, and agrees
with them.
[snip]
>> There is nothing Emacs-specific on those settings
>
> Each of those settings is there to support Emacs development.
How those settings benefit Emacs development? (In contrast to any other
project that uses git.) I asked that on my first message, but there is no
answer yet.
> It is true that other projects could use similar settings. For
> example, another project could also check that commit messages be in
> UTF-8. However, such a check is not appropriate for Git in general, as
> Git supports developers who use non-UTF-8 encodings for their commit
> messages. So we can't rely on vanilla Git to check that commit
> messages use UTF-8.
Okay, you explained why Emacs checks that UTF-8 is used on the commit
messages of their repo (I thought that git records the text encoding and
then converts it before display; that's basic functionality for a
distributed VCS, but if you say that an explicit setting is required for
avoiding making a mess of the VC history, I believe you.)
Now, what about the reasoning for the recent changes, in the context of
Emacs development? (Other than "they look like a good thing to me, so I
will put them on everyone's repo.")
next prev parent reply other threads:[~2016-02-01 20:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 20:22 Recommend these .gitconfig settings for git integrity Karl Fogel
2016-01-31 20:35 ` Eli Zaretskii
2016-01-31 21:37 ` Karl Fogel
2016-01-31 21:48 ` Paul Eggert
2016-02-01 15:42 ` Karl Fogel
2016-02-01 16:01 ` Óscar Fuentes
2016-02-01 16:24 ` Stefan Monnier
2016-02-01 16:39 ` Karl Fogel
2016-02-01 19:12 ` Stefan Monnier
2016-02-01 19:56 ` Paul Eggert
2016-02-01 20:28 ` Eli Zaretskii
2016-02-01 21:40 ` Stefan Monnier
2016-02-02 8:02 ` Paul Eggert
2016-02-02 8:17 ` John Wiegley
2016-02-02 12:58 ` Stefan Monnier
2016-02-02 15:49 ` Óscar Fuentes
2016-02-02 17:55 ` Paul Eggert
2016-02-02 18:48 ` Óscar Fuentes
2016-02-03 7:31 ` Paul Eggert
2016-02-03 16:20 ` Óscar Fuentes
2016-02-03 18:10 ` Paul Eggert
2016-02-03 20:50 ` Óscar Fuentes
2016-02-04 3:53 ` Stefan Monnier
2016-02-02 23:22 ` Karl Fogel
2016-02-03 0:20 ` Lars Ingebrigtsen
2016-02-03 2:16 ` John Wiegley
2016-02-03 2:26 ` Paul Eggert
2016-02-03 6:35 ` John Wiegley
2016-02-03 15:47 ` Eli Zaretskii
2016-02-03 17:40 ` Paul Eggert
2016-02-03 17:52 ` Eli Zaretskii
2016-02-03 18:04 ` Paul Eggert
2016-02-04 0:20 ` Lars Ingebrigtsen
2016-02-02 16:19 ` Eli Zaretskii
2016-02-01 18:39 ` John Wiegley
2016-02-01 16:35 ` Paul Eggert
2016-02-01 16:51 ` Óscar Fuentes
2016-02-01 17:40 ` Paul Eggert
2016-02-01 20:34 ` Óscar Fuentes [this message]
2016-02-01 18:09 ` Karl Fogel
2016-02-01 20:56 ` Óscar Fuentes
2016-02-01 21:07 ` Karl Fogel
2016-02-02 10:30 ` Tom
2016-02-02 15:37 ` Paul Eggert
2016-02-02 17:24 ` Tom
2016-02-02 17:54 ` Paul Eggert
2016-02-01 20:50 ` Karl Fogel
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=8737tci308.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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 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).