From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Jeff King <peff@peff.net>, 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 15:49:49 +0530 [thread overview]
Message-ID: <1503224389.2116.5.camel@gmail.com> (raw)
In-Reply-To: <20170820091807.l23h44gnjajfv5bn@sigill.intra.peff.net>
On Sun, 2017-08-20 at 05:18 -0400, Jeff King wrote:
> 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.
>
I would like to go with the "don't create commits with bogus
ident". "bogus idents" seem to go against the notion of a "content
tracker" which should *help* identifying the user who was the reason
behind the change. It shoudln't encourage users to create "anonymous
changes". Thus an "anonymous user" seems to completely obscure the
meaning of a "content tracker", at least in my opinion
Moreover, there's no tool that can satisfy *all* of it's users because
Humans are so diverse in their thoughts and behaviour.
--
Kaartic
next prev parent reply other threads:[~2017-08-20 10:19 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
2017-08-20 10:19 ` Kaartic Sivaraam [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1503224389.2116.5.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=noloader@gmail.com \
--cc=peff@peff.net \
/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.
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.