Re: [PATCH] contrib: remote-helpers: add move warnings (v2.0)

Felipe Contreras [off-list ref] writes:

The tools are now maintained out-of-tree, and they have a regression in
v2.0.

You seem not to understand at all what a regression is.

My understanding is that versions of remote-hg shipped with all
versions of Git did not work with Hg 3.0, so not working with Hg 3.0
is a regression in v2.0 at all.  A recent report was about Hg 3.0
not working with 1.9.3, but I think you earlier said all versions of
Git does not work with Hg 3.0, and I can believe it.  That is hardly
a regression.

You could argue that Hg has a new regression to its external users
of its API when it went to 3.0.  We actually had a similar breakage
in 1.5.4, where it was reported late in the cycle after -rc0 [*1*]
that cgit that linked with our internal API libgit.a was broken by a
change on our side, which resulted in us fixing the breakage (even
though technically you may be able to say that it was cgit's fault
to link with libgit.a in the first place) with 18125644 (Move
sha1_file_to_archive into libgit, 2008-01-14) very late in the
cycle.  Calling that a regression in cgit would have been insane,
even if we did not patch our side up to accomodate it.

Stop this idiocy.


[References]

*1* http://thread.gmane.org/gmane.comp.version-control.git/70117/focus=71064

Junio C Hamano wrote:

Felipe Contreras [off-list ref] writes:

quoted

The tools are now maintained out-of-tree, and they have a regression in
v2.0.

You seem not to understand at all what a regression is.

My understanding is that versions of remote-hg shipped with all
versions of Git did not work with Hg 3.0, so not working with Hg 3.0
is a regression in v2.0 at all.

I explained to you multiple times already that is a different issue, but
it somehow doesn't get through your skull.

Let me try a different approach.

git-remote-bzr has a regression in Git v2.0.

Did you get the BAZAAR part? That's right, this is unrelated to
Mercurial v3.0 because it doesn't have anything to do with Mercurial.

*BOTH* git-remote-hg and git-remote-bzr have a regression in Git v2.0.

A recent report was about Hg 3.0 not working with 1.9.3, but I think
you earlier said all versions of Git does not work with Hg 3.0, and I
can believe it.  That is hardly a regression.

You could argue that Hg has a new regression to its external users
of its API when it went to 3.0.  We actually had a similar breakage
in 1.5.4, where it was reported late in the cycle after -rc0 [*1*]
that cgit that linked with our internal API libgit.a was broken by a
change on our side, which resulted in us fixing the breakage (even
though technically you may be able to say that it was cgit's fault
to link with libgit.a in the first place) with 18125644 (Move
sha1_file_to_archive into libgit, 2008-01-14) very late in the
cycle.  Calling that a regression in cgit would have been insane,
even if we did not patch our side up to accomodate it.

Stop this idiocy.

Sigh, you just don't seem to understand that you are thinking about a
different issue. I don't think there's any other way I can explain it to
you.

-- 
Felipe Contreras

On Tue, May 13, 2014 at 3:22 PM, Felipe Contreras
[off-list ref] wrote:

Junio C Hamano wrote:

quoted

Felipe Contreras [off-list ref] writes:

quoted

The tools are now maintained out-of-tree, and they have a regression in
v2.0.

You seem not to understand at all what a regression is.

My understanding is that versions of remote-hg shipped with all
versions of Git did not work with Hg 3.0, so not working with Hg 3.0
is a regression in v2.0 at all.

I explained to you multiple times already that is a different issue, but
it somehow doesn't get through your skull.

Could you please calm down and adjust your behavior.
This constant hostility and rudeness makes the mailing list very unpleasant.

Let me try a different approach.

git-remote-bzr has a regression in Git v2.0.

Did you get the BAZAAR part? That's right, this is unrelated to
Mercurial v3.0 because it doesn't have anything to do with Mercurial.

*BOTH* git-remote-hg and git-remote-bzr have a regression in Git v2.0.

quoted

A recent report was about Hg 3.0 not working with 1.9.3, but I think
you earlier said all versions of Git does not work with Hg 3.0, and I
can believe it.  That is hardly a regression.

You could argue that Hg has a new regression to its external users
of its API when it went to 3.0.  We actually had a similar breakage
in 1.5.4, where it was reported late in the cycle after -rc0 [*1*]
that cgit that linked with our internal API libgit.a was broken by a
change on our side, which resulted in us fixing the breakage (even
though technically you may be able to say that it was cgit's fault
to link with libgit.a in the first place) with 18125644 (Move
sha1_file_to_archive into libgit, 2008-01-14) very late in the
cycle.  Calling that a regression in cgit would have been insane,
even if we did not patch our side up to accomodate it.

Stop this idiocy.

Sigh, you just don't seem to understand that you are thinking about a
different issue. I don't think there's any other way I can explain it to
you.

--
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Ronnie Sahlberg wrote:

Could you please calm down and adjust your behavior.  This constant
hostility and rudeness makes the mailing list very unpleasant.

I explaind that to him multiple times. In the mail I replied to he is
once again assuming I'm a *insert-your-favorite-non-smart-adjective*,
and explaining to me what a regression is.

How many times must one repeat something before one is entitled so thay
something is not "getting through the skull" of another person? 5? 10?
20?

But fine, let's assume I do have to adjust my behavior. Maybe I should
have said "it doesn't register in your brain", or just "it fails to grab
your attention".

But if I have to adjust for saying that (which was true), what do you
say to Junio for saying this? (which was not)

quoted

Stop this idiocy.

I presume nothing, because Junio is a riskier target.

-- 
Felipe Contreras

On Tue, May 13, 2014 at 4:37 PM, Felipe Contreras
[off-list ref] wrote:

Ronnie Sahlberg wrote:

quoted

Could you please calm down and adjust your behavior.  This constant
hostility and rudeness makes the mailing list very unpleasant.

I explaind that to him multiple times. In the mail I replied to he is
once again assuming I'm a *insert-your-favorite-non-smart-adjective*,
and explaining to me what a regression is.

How many times must one repeat something before one is entitled so thay
something is not "getting through the skull" of another person? 5? 10?
20?

But fine, let's assume I do have to adjust my behavior. Maybe I should
have said "it doesn't register in your brain", or just "it fails to grab
your attention".

But if I have to adjust for saying that (which was true), what do you
say to Junio for saying this? (which was not)

I know I shouldn't but I will respond anyway.

The problem is about you and your behaviour. Not Junio or anyone else.

Please adjust and stop your constant hostile, confrontational and
abusive behavior on this mailinglist.
Your behavior is not a winning strategy and will only result in
alienating you and impair your interactions with
the rest of the git community.


If anything, Junio have shown an amazing amount of patience and
restraint with you.
I would not have tolerated your kind of behavior in any project I am
maintainer for.

quoted

quoted

Stop this idiocy.

I presume nothing, because Junio is a riskier target.

Please follow Junio's advice. It will benefit both you as well as all
other participants in the community.

Ronnie Sahlberg wrote:

On Tue, May 13, 2014 at 4:37 PM, Felipe Contreras
[off-list ref] wrote:

quoted

But if I have to adjust for saying that (which was true), what do you
say to Junio for saying this? (which was not)

I know I shouldn't but I will respond anyway.

The problem is about you and your behaviour. Not Junio or anyone else.

Right. So when I say something moderately aggressive (but true), I'm the
problem, when Junio says something worst (and false), he is not.

Got it.

-- 
Felipe Contreras