archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <>
To: Linus Torvalds <>,
	Felipe Contreras <>
Cc:, "Richard Hansen" <>,
	"Jeff King" <>,, "Dusty Phillips" <>,
	"Antoine Pelisse" <>,
	"John Keeping" <>,
	"Christophe Simonis" <>,
	"Torsten Bögershausen" <>
Subject: Re: Should git-remote-hg/bzr be part of the core?
Date: Mon, 12 May 2014 02:42:17 -0500	[thread overview]
Message-ID: <53707b5955034_2b5710592f8aa@nysa.notmuch> (raw)
In-Reply-To: <>

Linus Torvalds wrote:
> On May 12, 2014 8:35 AM, "Felipe Contreras" <>
> wrote:
> >
> > This move is already
> > under way, but suddenly Junio changed his mind.
> That "suddenly" wouldn't have anything to do with you being an ass and
> difficult as usual, arguing about everything and just generally being
> contrary?

No, here's where the thread started (A):

Here I wasn't being an ass:

Here I wasn't being an ass either:

Neither here:

Nor here:

Nor here:

Not an ass here:

And not here either:

Then Junio *suddenly* changed his mind (B):

That is the sequence of mails (A..B) where I responded, and I wasn't an
ass in eithe one of those, so whatever made Junio change his mind
happened in that interum, and it wasn't me "being an ass".

I bet you made that statement without even botherting to read the
thread. Go on, read the thread, tell where exactly me "being an ass"
made Junio change his mind from A, to B.

Nah, you wouldn't do that, backing up your claims take time, and you are
not willing to spend time on this issue. Even if you were to try to back
up your claim, you couldn't, becasue it's not true. It's much easier to
just throw good sounding baseless claims and walk away.

> Felipe, stop this stupid blaming of everybody but yourself.

Show me evidence that this decision was my fault. Junio certainly hasn't
said so. You just have no idea what we are talking about.

> You make absolutely everything be this horrible disaster, you redefine
> words ("regression") to be whatever you need/want them to be to be

git-remote-hg and git-remote-bzr will likely break in Git v2.0 in certain
situations where they wouldn't in v1.9, or v1.8. Call it whatever you
want. I call that a regression.

> Seriously. Don't try to make this about Junio somehow being the problem.

So Junio is perfect. Got it.

If you don't have the time to actually read the rationale behind Junio's
decision, how would you even know he made the right one? You are just
blindly assuming he is right, and therefore he is not the problem.

What if he was wrong? Nah, that's impossible. Right?

Felipe Contreras

  parent reply	other threads:[~2014-05-12  7:42 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] ` <>
2014-05-12  7:42   ` Felipe Contreras [this message]
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]   ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53707b5955034_2b5710592f8aa@nysa.notmuch \ \ \ \ \ \ \ \ \ \ \ \

* 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).