hg 4.6 breaks hg-git and evolve plugins?
Matt Harbison
mharbison72 at gmail.com
Fri Aug 17 04:16:39 UTC 2018
On Wed, 08 Aug 2018 09:38:56 -0400, Jesus Cea <jcea at jcea.es> wrote:
> On 20/05/18 12:59, Paul Morelle wrote:
>> I have proposed these patches to hg-git to fix the problems that I was
>> having with the new hg version, but they haven't been merged yet.
>>
>> https://groups.google.com/forum/#!topic/hg-git/XDQrbr4FhA0 [PATCH 1
>> of 2] gitrepo: add missing 'intents' keyword (from hg 4.6) to
>> gitrepo.__init__
>> https://groups.google.com/forum/#!topic/hg-git/5lcPUzlxEFc [PATCH 2
>> of 2] git_handler: use repo.__getitem__ instead of (removed)
>> repo.changectx
>
> Thanks for the patches, Paul.
>
> I actually think that "hg-git" deserves more love. For some of us, it is
> what allows us to keep using Mercurial instead of "downgrading" to git.
> It should be better maintained and follow current Mercurial better.
>
> I appreciate the effort and gives me value every day, all of us are
> volunteers, but breaking constantly is... stressful. And it is painfully
> slow too :(.
>
> Maybe some mercurial core devels, knowing that hg-git provides huge
> value to mercurial ecosystem, could help hg-git to cope with mercurial
> API churning.
I'm not sure that much can be done about API churn, without bundling it as
a built in extension. I don't follow the development on that, so I'm not
sure if there's a reason it hasn't been bundled. It might even make it a
little easier to tie together with LFS.
But someone at work enabled it in our setup scripts, and I tend to be the
first to upgrade, so I feel your pain about it not always working on
upgrades.
More information about the Mercurial
mailing list