Re: [PATCH] remote-helpers: point at their upstream repositories

[Felipe Contreras <felipe.contreras@gmail.com>]

Jeff King wrote:
> On Sat, May 17, 2014 at 12:25:30AM -0500, Felipe Contreras wrote:
> 
> > > I agree with the line of reasoning you laid out in your email,
> > > especially:
> > 
> > What a shock.
> 
> Please stop with these unproductive and rude comments.

I am sorry, but the fact of the matter is that you *always* agree with
Junio.

> > > I hadn't thought of the rename idea, and it would address the concerns I
> > > brought up. I do think "obsolete" is the wrong word, as it sends the
> > > wrong message. The helpers are not obsolete; it is our _copy_ of them
> > > that is.
> > 
> > Originally you said you would respect if I wanted the code out
> > for v2.0, I said I would like it out at some point, not necessarily in
> > v2.0. Junio said he was fine with that, but the proposals above don't do
> > that.
> > 
> > Now it seems you are changing your mind and you are OK with the code
> > remaining in.
> 
> My concerns were with people not noticing the README. Removing the code
> entirely is the way I thought of to address that. Junio suggested
> another way, which I would also be fine with. And it seems like a
> friendlier way than removal to handle it for v2.0, if we are going to
> remove the code entirely post-v2.0.

I don't see what is friendlier about this:

 % sudo pacman -Syu
 % cd ~/dev/my-hg-repo
 % git fetch
 fatal: Unable to find remote helper for 'hg'

The users will scratch their heads, wonder what's going on, investigate
themselves, and eventually they'll have to decide how to fix the issue
properly, and how to report it.

On the other hand:

 % git fetch
 WARNING: git-remote-hg is now maintained independently.
 WARNING: For more information visit https://github.com/felipec/git-remote-hg
 searching for changes
 no changes found

You think that's less friendly?

If you think so, I think you are totally biased towards whatever happens
to be the opinion of one person.

> As before, if your desire is to have the code out for v2.0, then say so.
> I think we should respect such a request.

As I said before, I do not wish the code to be removed for v2.0, I would
like to have only a warning. Either way, do whatever you want for v2.0,
it's your users you are hurting.

But if I do not hear *from Junio* that the code will be removed entirely
post-v2.0, hopefully replaced with stubs (which is obviously the most
user-friendly thing to do), I'll do what I said I'll do.

-- 
Felipe Contreras