git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: Please fix the useless email prompts
Date: Sun, 20 Aug 2017 05:18:07 -0400	[thread overview]
Message-ID: <20170820091807.l23h44gnjajfv5bn@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH8yC8mpPRN2y1k07_Jk9QP88=gpLKNWfV3W0QQwXTWxyL5STQ@mail.gmail.com>

On Sat, Aug 19, 2017 at 02:02:09PM -0400, Jeffrey Walton wrote:

> > Hasn't this been asked and answered already?
> >
> >     https://public-inbox.org/git/CACBZZX4vEOD-4a-eK-uBxmFrb1GLSvJKxHW51whCSbCZdh7amQ@mail.gmail.com/
> 
> Its 2017. I'd like the tools to work for me instead of me working for the tools.

Ironically, Git used to behave as you requested in 2005. After being
bombarded with complaints about how Git was too lax in creating commits
with bogus ident information, we changed it in 2012. So I don't think
"it's 2017" carries any weight as an argument.

There are numerous discussions in the archive on this. But my
recollection is that the conclusion is:

  - stricter ident checking on balance saves more headaches than it
    causes, just in terms of numbers

  - the headaches solved by stricter checking are hard to fix (because
    you unknowingly bake cruft into commit objects, and fixing that
    requires a history rewrite)

  - the headaches caused by stricter checking are easy to fix (they're
    obvious when they happen, and "git -c" lets you provide a dummy
    value to override).

We can revisit any of those conclusions, but I'd want to see a
thoughtful discussion of the tradeoffs raised in past rounds, not just
"the current behavior is inconvenient for me".

-Peff

  parent reply	other threads:[~2017-08-20  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 15:10 Please fix the useless email prompts Jeffrey Walton
2017-08-19 16:36 ` Junio C Hamano
2017-08-19 18:02   ` Jeffrey Walton
2017-08-19 19:17     ` Patryk Obara
2017-08-20  9:18     ` Jeff King [this message]
2017-08-20 10:19       ` Kaartic Sivaraam
2017-08-20 12:40       ` Andrew Ardill
2017-08-20 21:57         ` Anatolii Borodin
2017-08-20 23:32           ` Andrew Ardill
2017-08-20 23:56             ` Junio C Hamano
2017-08-23 15:35               ` Jeff King
2017-08-23 17:36                 ` Junio C Hamano
2017-08-20 21:50 ` Anatolii Borodin

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170820091807.l23h44gnjajfv5bn@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=noloader@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://80x24.org/mirrors/git.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).