git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: Re: [PATCH] teach the user to be nice to git and let him say please sometimes
Date: Mon, 13 May 2013 15:30:35 +0200	[thread overview]
Message-ID: <20130513133035.GA3561@book-mint> (raw)
In-Reply-To: <CACsJy8A+vjtwnB0LStVS3Q9v2JaKcMDa0sATr9H==X3EhQt6Jg@mail.gmail.com>

On Sun, May 12, 2013 at 05:23:15PM +0700, Duy Nguyen wrote:
> On Sun, May 12, 2013 at 3:20 AM, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> > Since ages we do not care about our program enough. Lets not treat them
> > as slaves anymore and say please.
> >
> > Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
> > Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> > Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> > Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
> > Signed-off-by: Johan Herland <johan@herland.net>
> 
> A product of Git Berlin Meetup?

Yep :-)

> > +static void check_politeness(const char *cmd)
> > +{
> > +       const char *user_config;
> > +       struct strbuf buf = STRBUF_INIT;
> > +
> > +       if (getenv("GIT_POLITENESS_CHECK_PASSED"))
> > +               return;
> > +
> > +       setenv("GIT_POLITENESS_CHECK_PASSED", "Yes", 1);
> > +
> > +       git_config_early(read_polite_counter, NULL, NULL);
> > +       if (!strcmp(cmd, "please")) {
> > +               impolite_counter = 0;
> > +               polite_counter++;
> > +       } else {
> > +               impolite_counter++;
> > +               polite_counter = 0;
> > +       }
> > +
> > +       if (impolite_counter > 10)
> > +               die("Error: Learn some manners, say please some time!");
> > +       if (polite_counter > 10)
> > +               die("Error: Too many please! I don't believe you.");
> 
> NAK. If we truly care, we need better AI here!

I agree but this patches goal was to implement the basic politeness
infrastructure. We planned to add more features, like inter-repository
jealousy, later. For inter-repository jealousy git would complain if you
worked more with one repository than others you cloned and you'd for
example sometimes need a double please to satisfy it.

Cheers Heiko

  reply	other threads:[~2013-05-13 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11 20:20 [PATCH] teach the user to be nice to git and let him say please sometimes Heiko Voigt
2013-05-12 10:07 ` Ramkumar Ramachandra
2013-05-12 10:23 ` Duy Nguyen
2013-05-13 13:30   ` Heiko Voigt [this message]
2013-05-13 13:58     ` Duy Nguyen
2013-05-12 21:19 ` Junio C Hamano
2013-05-13 13:44   ` Heiko Voigt
2013-05-13 20:40     ` Thomas Rast
2013-05-13 20:47       ` Junio C Hamano

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=20130513133035.GA3561@book-mint \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@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.
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 NNTP newsgroup(s).