git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: David Kastrup <dak@gnu.org>,
	Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Michael Haggerty" <mhagger@alum.mit.edu>,
	git@vger.kernel.org, git-fc@googlegroups.com,
	"Richard Hansen" <rhansen@bbn.com>,
	"Torsten Bögershaus" <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 12:12:08 -0500	[thread overview]
Message-ID: <537100e8b6682_222d129730829@nysa.notmuch> (raw)
In-Reply-To: <87mwenuond.fsf@fencepost.gnu.org>

David Kastrup wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
> 
> > Then there's no point in reading what else you have to say. Whatever
> > reasons you might have to agree with Junio are known only to you, thus
> > your "agreement" is opaque and meaningless.
> 
> Let me spell it out for you.  Michael states "I agree with Junio.  There
> are good technical arguments for and against moving git-remote-hg out of
> contrib."  Since there are arguments for both sides, the decision boils
> down to a judgment call.  Michael states that he condones the choice
> Junio made, based on the reasoning he gave.

Junio didn't give any reasoning, he deferred by saying "that reason some
other guy gave" and he never explained which reason that was.

Which is why I'm pretty sure Michael Haggery does not have actually any
reason.

He even admitted almost as much by saying he doesn't really care much
about these "small technical issues", which are not important to him.

So until Michael explains his reasons, I'll assume he has none. And so
should any rational person.

-- 
Felipe Contreras

  reply	other threads:[~2014-05-12 17:23 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 [this message]
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

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=537100e8b6682_222d129730829@nysa.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=apelisse@gmail.com \
    --cc=christophe@kn.gl \
    --cc=dak@gnu.org \
    --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=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).