Re: [PATCH 2/3] http-push: fix construction of hex value from path

2 messages, 2 authors, 2017-10-04 · open the first message on its own page

Re: [PATCH 2/3] http-push: fix construction of hex value from path

From: Junio C Hamano <hidden>
Date: 2017-10-04 05:20:18

Junio C Hamano [off-list ref] writes:
Jeff King [off-list ref] writes:
quoted
quoted
Moreover, this is in the webdav-based "dumb http" push code path,
which I do not trust much at all.  I wonder if we could retire it
completely (or at least provide an option to turn it off).
I would really like that, too. It has been the cause of a lot of pain
when working with the smart code, and I am not at all surprised to find
a bug of this magnitude lurking in it. I'd _hoped_ this could show that
the system has been unusably broken for years, which would give us
confidence to turn it off. :) But per your paragraph above, people could
very easily still have been happily using it in the meantime.
Same here.  Perhaps we should deliberately and silently break it and
see who screams?
Hopefully it should be obvious but just for people with unreasonable
expectations, I should clarify that the above needs a smiley ;-).

Re: [PATCH 2/3] http-push: fix construction of hex value from path

From: Jeff King <hidden>
Date: 2017-10-04 05:26:47

On Wed, Oct 04, 2017 at 02:20:05PM +0900, Junio C Hamano wrote:
Junio C Hamano [off-list ref] writes:
quoted
Jeff King [off-list ref] writes:
quoted
quoted
Moreover, this is in the webdav-based "dumb http" push code path,
which I do not trust much at all.  I wonder if we could retire it
completely (or at least provide an option to turn it off).
I would really like that, too. It has been the cause of a lot of pain
when working with the smart code, and I am not at all surprised to find
a bug of this magnitude lurking in it. I'd _hoped_ this could show that
the system has been unusably broken for years, which would give us
confidence to turn it off. :) But per your paragraph above, people could
very easily still have been happily using it in the meantime.
Same here.  Perhaps we should deliberately and silently break it and
see who screams?
Hopefully it should be obvious but just for people with unreasonable
expectations, I should clarify that the above needs a smiley ;-).
Yes, I was surprised to see it without one. :)

More seriously, is there any interest in marking it as deprecated in the
release notes and issuing a warning when it's used for a few cycles?

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help