git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	Felipe Contreras <felipe.contreras@gmail.com>
Cc: Marius Storm-Olsen <mstormo@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] contrib: remote-helpers: add move warnings (v2.0)
Date: Wed, 14 May 2014 15:51:55 -0500	[thread overview]
Message-ID: <5373d76b965c1_592416ad2f8ca@nysa.notmuch> (raw)
In-Reply-To: <xmqqha4sjelx.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
> 
> > Junio C Hamano wrote:
> >> So at this point, I would have to say that the users of remote-hg is
> >> taken hostage by its author.
> >
> > The users of remote-hg are being affected negatively *because* of your
> > decisions.
> >
> > You have the power to help them by answering a simple question. Yet you
> > refuse to do that.
> >
> > It's all on you.
> 
> That is exactly what I would call "taking users hostage".
> 
> I think I already answered that one question:

> in $gmane/248853 with:
> 
>     You certainly are acting like one, aren't you?
> 
> Do you need more?

You know full well this is not the question I asked you repeatedly. Stop
trying to spin the readers.

I asked you here:
http://article.gmane.org/gmane.comp.version-control.git/248683

And here:
http://article.gmane.org/gmane.comp.version-control.git/248348

And here:
http://article.gmane.org/gmane.comp.version-control.git/248368

I made it clear you were not answering the qustion here:
http://article.gmane.org/gmane.comp.version-control.git/248685

And here:
http://article.gmane.org/gmane.comp.version-control.git/248701

And here (apparently deleted mail):
1400013572-30232-1-git-send-email-felipe.contreras@gmail.com

And probably many other times.

And I will ask you once again.

Please answer this *one* question:

1) Please clarify the reason why you blocked the graduation of remote
   helpers. Please give the full rationale and do not point to other
   mails, or other peoples' explanations. If necessary attach such
   explanations to your full reasoning.

This is the *one* question you have refused to answer over and over.

-- 
Felipe Contreras

  reply	other threads:[~2014-05-14 21:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 21:29 [PATCH] contrib: remote-helpers: add move warnings (v2.0) Felipe Contreras
2014-05-13 22:02 ` Junio C Hamano
2014-05-13 22:22   ` Felipe Contreras
2014-05-13 22:41     ` Junio C Hamano
2014-05-13 22:47       ` Felipe Contreras
2014-05-14  2:16         ` Marius Storm-Olsen
2014-05-14 19:06           ` Junio C Hamano
2014-05-14 19:39             ` Felipe Contreras
2014-05-14 20:21               ` Junio C Hamano
2014-05-14 20:51                 ` Felipe Contreras [this message]
2014-05-13 23:11     ` Ronnie Sahlberg
2014-05-13 23:37       ` Felipe Contreras
2014-05-14 16:57         ` Ronnie Sahlberg
2014-05-14 19:26           ` 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=5373d76b965c1_592416ad2f8ca@nysa.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mstormo@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).