From: John Wiegley <jwiegley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Karl Fogel" <kfogel@red-bean.com>,
"Óscar Fuentes" <ofv@wanadoo.es>, "Eli Zaretskii" <eliz@gnu.org>,
"Stefan Monnier" <monnier@IRO.UMontreal.CA>,
"Emacs Development" <Emacs-devel@gnu.org>
Subject: Re: Recommend these .gitconfig settings for git integrity.
Date: Tue, 02 Feb 2016 00:17:08 -0800 [thread overview]
Message-ID: <m2twlrfrwb.fsf@newartisans.com> (raw)
In-Reply-To: <56B06282.2050701@cs.ucla.edu> (Paul Eggert's message of "Tue, 2 Feb 2016 00:02:10 -0800")
>>>>> Paul Eggert <eggert@cs.ucla.edu> writes:
> Should we pay the checking overhead to catch these reliability and security
> problems? That's the question. Emacs developers who are using this setting
> report that the overhead is small enough as to not be a significant issue,
> which suggests that the extra checking is a good idea.
Even still, this is purely a Git matter, and not an Emacs matter. This choice
shouldn't be automatically made on user's machine, however beneficial. It's
been recommended now in git-workflow, but should not be applied automatically.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-02-02 8:17 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2twlrfrwb.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=johnw@gnu.org \
--cc=kfogel@red-bean.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=ofv@wanadoo.es \
/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.