git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Error using git-remote-hg

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 13, 2014, 18:21 UTC
Message-ID
<5372629ed59b9_7774d392f8f1@nysa.notmuch>
In-Reply-To
<xmqq61l9powd.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> It is time to catch regressions by asking wider audiences who do not
> normally follow Git development (i.e. those who are not the ones that
> follow 'master' and rebuild/install it once or twice a week for their
> daily use).
And you have one of those regressions in Git v2.0.
Show 5 quoted lines
> My understanding is that versions of remote-hg shipped with all
> versions of Git did not work with Hg 3.0, so 58aee08 is not a
> regression fix at all.  Is working with Hg 3.0 at such a high priority
> that it makes it worth to slip the whole release schedule by a few
> weeks?  I do not think so.

It is in the contrib/ area, you don't need to slip the schedule for something that is not part of the core.

Moreover, it *CANNOT POSSIBLY INTRODUCE REGRESSIONS*. I bet my reputation on that.

Some time ago I asked you to trust my judgement and introduce changes late into a release, and I told you there wouldn't be any problems, and to trust me. If any problems arise I wouldn't be asking for something like that again.

Well, I was right, there were no problems. And I'm right this time too, there would be no issues.

But you don't care about reality and facts. You don't care about the intent behind the release-candidates rule, you would rather follow the rule blindly.

> Regarding the commit in question, I asked Felipe a question and
> never got a straight answer.

Nor will you get one, because thanks to your stupid decision for which you still haven't provided a rationale, the git-remote-hg and git-remote-hg are no longer maintained in git.git.

If you hadn't made such a move, you would have your answer, the fix would be properly explained, the regression fixed, and all your users would be happy that git-remote-hg and git-remote-bzr get distributed by default.

-- 
Felipe Contreras
Previous: Junio C HamanoNext: William Giokas
Message 7 of 13 in “Error using git-remote-hg”
  1. Charles BrossolletMay 12, 2014
  2. Torsten BögershausenMay 12, 2014
  3. Felipe ContrerasMay 12, 2014
  4. Charles BrossolletMay 13, 2014
  5. Torsten BögershausenMay 13, 2014
  6. Junio C HamanoMay 13, 2014
  7. Felipe ContrerasMay 13, 2014
  8. William GiokasMay 13, 2014
  9. Felipe ContrerasMay 13, 2014
  10. William GiokasMay 13, 2014
  11. Felipe ContrerasMay 13, 2014
  12. William GiokasMay 13, 2014
  13. Felipe ContrerasMay 13, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.