git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2 01/17] contrib: remove outdated README
Date: Wed, 14 May 2014 14:51:09 +0200	[thread overview]
Message-ID: <CAGK7Mr63X3+XXuRUEcBwwnwrOrbip8VUebtL-tM3R8PYBPEXuQ@mail.gmail.com> (raw)
In-Reply-To: <53729ccf26bb0_34aa9e53047f@nysa.notmuch>

>> I have had patches and contributions rejected in the past, sometimes
>> rudely. Same has happened to many others, if you contribute long
>> enough, it is pretty much guaranteed that it will happen to you.
>> Maintainer is wrong, or you are wrong, or someone is just having a bad
>> day.
>
> This is not about a couple of patches I worked in a weekend being
> rejected. This is about the work I've been doing since the past two
> years almost like a full-time job dropped to the floor with no
> explanation at all. I started with the expectation that they were going
> to move to the core, because Junio said so, then he changed his mind and
> didn't want to explain his reasoning.
>
> It's not just a bad day.

Here are two posts where Junio and Michael Haggerty explain the
reasoning to you:

- http://article.gmane.org/gmane.comp.version-control.git/248727
- http://article.gmane.org/gmane.comp.version-control.git/248693

Basically, in your case it boils down to your social manners. Despite
the (good) work you did, many people think the community and git as a
whole as more to loose by having to deal with your theatrics,
especially since you try to take everyone hostage of your situations.
No amount of "arguing" (calling it "ad hominem" etc) will change
anything at this point, you have to accept that your social actions
have a big part of responsibility in this.

IMHO, you should change your behavior into a more respectful one and
give people some time to discover you changed, otherwise it is
innevitable that you'll just get banned/ignored by mostly everyone.

We spent way too much energy dealing with these silly issues, please
find a way to deal with it that doesn't annoy everyone and doens't
affect the friendlyness of the mailing list.

Philippe

  reply	other threads:[~2014-05-14 12:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 19:11 [PATCH v2 00/17] contrib: cleanup Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 01/17] contrib: remove outdated README Felipe Contreras
2014-05-09 19:58   ` Junio C Hamano
2014-05-09 21:54     ` Felipe Contreras
2014-05-13 18:10       ` Martin Langhoff
2014-05-13 18:27         ` Junio C Hamano
2014-05-13 18:54           ` Felipe Contreras
2014-05-13 21:05             ` Junio C Hamano
2014-05-13 21:35               ` Martin Langhoff
2014-05-13 22:29                 ` Felipe Contreras
2014-05-14 12:51                   ` Philippe Vaucher [this message]
2014-05-14 19:35                     ` Felipe Contreras
2014-05-14 19:55                       ` Martin Langhoff
2014-05-14 20:26                       ` Jeff King
2014-05-14 21:26                         ` Felipe Contreras
2014-05-14 20:59                       ` Junio C Hamano
2014-05-14 23:28                         ` Felipe Contreras
2014-05-14 23:50                           ` Martin Langhoff
2014-05-14 23:48                             ` Felipe Contreras
2014-05-15 22:56                           ` Junio C Hamano
2014-05-16  8:08                             ` Felipe Contreras
2014-05-16  8:59                               ` William Giokas
2014-05-16 10:21                                 ` Felipe Contreras
2014-05-16 11:25                                   ` William Giokas
2014-05-16 12:20                                     ` Felipe Contreras
2014-05-13 22:52               ` Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 02/17] contrib: remove 'vim' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 03/17] contrib: remove 'emacs' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 04/17] contrib: remove 'diffall' Felipe Contreras
2014-05-09 19:27   ` Tim Henigan
2014-05-09 19:11 ` [PATCH v2 05/17] contrib: remove 'hg-to-git' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 07/17] contrib: remove 'stats' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 08/17] contrib: remove 'convert-objects' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 09/17] contrib: remove 'git-shell-commands' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 10/17] contrib: reomve 'thunderbird-patch-inline' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 11/17] contrib: remove 'workdir' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 12/17] contrib: remove 'svn-fe' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 13/17] contrib: remove 'rerere-train' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 14/17] contrib: remove 'remotes2config' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 15/17] contrib: remove 'persistent-https' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 16/17] contrib: remove 'git-resurrect' Felipe Contreras
2014-05-09 19:11 ` [PATCH v2 17/17] contrib: remove 'contacts' Felipe Contreras

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=CAGK7Mr63X3+XXuRUEcBwwnwrOrbip8VUebtL-tM3R8PYBPEXuQ@mail.gmail.com \
    --to=philippe.vaucher@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.langhoff@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).