From: Felipe Contreras <felipe.contreras@gmail.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Michael Haggerty" <mhagger@alum.mit.edu>,
"Git Mailing List" <git@vger.kernel.org>,
git-fc <git-fc@googlegroups.com>,
"Richard Hansen" <rhansen@bbn.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"Antoine Pelisse" <apelisse@gmail.com>,
"Christophe Simonis" <christophe@kn.gl>,
"Dusty Phillips" <dusty@linux.ca>, "Jeff King" <peff@peff.net>,
"John Keeping" <john@keeping.me.uk>
Subject: Re: Should git-remote-hg/bzr be part of the core?
Date: Mon, 12 May 2014 11:40:08 -0500 [thread overview]
Message-ID: <5370f968d378c_222d12973081b@nysa.notmuch> (raw)
In-Reply-To: <CAHVLzckDnfFQpZ-u8qdmKqaCNk62b_K_yinfamBPgm1oST1eLQ@mail.gmail.com>
Paolo Ciarrocchi wrote:
> On Mon, May 12, 2014 at 2:48 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> > Paolo Ciarrocchi wrote:
> > > On Mon, May 12, 2014 at 11:42 AM, Michael Haggerty <mhagger@alum.mit.edu>wrote:
>
> > > While I agree with you the this project is managed in a bit conservative
> > > way
> >
> > Only a bit? I don't think I've been involed in a more conservative open
> > source project.
> >
> > > you should really improve how you communicate with other developers,
> > > it's such a pity your contributions are some times not included in
> > > git.git just because of your attitude.
> >
> > But that's a theory. You don't *know* that they would have been included
> > had I used a different attitude.
>
> Well, you could at least try to act and communicate differently.
I have, it doesn't make a difference.
> > In fact, people have contacted me privately saying similar things, and
> > I'll give you the same challenge I gave them. If you think a different
> > attitude would get my patches in, how about *you* write the commit
> > messages and the discussions for one of my stuck patch series. I'll send
> > the mails as if I had written the content.
>
> No, sorry but I'm NOT interested in lying to git community.
Yeah, that's what I thought. I know what the result of such experiment
would be though.
--
Felipe Contreras
prev parent reply other threads:[~2014-05-12 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:34 Should git-remote-hg/bzr be part of the core? Felipe Contreras
[not found] ` <CA+55aFwf9iAKxbvdPV9Up_T709KwBXJWW4g-F829CRQP4YkivQ@mail.gmail.com>
2014-05-12 7:42 ` Felipe Contreras
2014-05-12 8:12 ` Felipe Contreras
2014-05-12 10:28 ` Stefan Beller
2014-05-12 12:05 ` Felipe Contreras
2014-05-12 9:42 ` Michael Haggerty
2014-05-12 10:35 ` Dennis Kaarsemaker
2014-05-12 10:37 ` Felipe Contreras
2014-05-12 12:05 ` Michael Haggerty
2014-05-12 12:29 ` Felipe Contreras
2014-05-12 13:12 ` David Kastrup
2014-05-12 17:12 ` Felipe Contreras
2014-05-12 13:43 ` Michael Haggerty
2014-05-12 17:13 ` Felipe Contreras
2014-05-12 11:00 ` David Kastrup
[not found] ` <CAHVLzcmqdkf4fMTok+HsXcDOQ5Oz2QdZti3FuzgBUa2T6AWnfA@mail.gmail.com>
2014-05-12 12:48 ` Felipe Contreras
2014-05-12 13:45 ` Paolo Ciarrocchi
2014-05-12 16:13 ` Stefan Beller
2014-05-12 16:40 ` Felipe Contreras [this message]
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=5370f968d378c_222d12973081b@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=apelisse@gmail.com \
--cc=christophe@kn.gl \
--cc=dusty@linux.ca \
--cc=git-fc@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=mhagger@alum.mit.edu \
--cc=paolo.ciarrocchi@gmail.com \
--cc=peff@peff.net \
--cc=rhansen@bbn.com \
--cc=tboegi@web.de \
/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).