Notices tagged with mercurial

♲ @JordiGH@mathstodon.xyz: «There is no theoretical reason you can’t maintain two histories—-e.g. when rebasing have a “rebase-merge” commit that has the hash of the other tree, and optionally keep that history around in the git repo. Then you could do a ‘git blame —orig’ or whatever to switch between immutable and cleaned up history.

No VCS I’m aware of supports this. But they COULD.»

news.ycombinator.com/item?id=1…

Friend, let me introduce you to #Mercurial #Evolve...

youtu.be/4OlDm3akbqg?t=840

Huh #PyQt is using #Mercurial:

https://www.riverbankcomputing.com/hg/

It's so nice to find hg usage in the wild. Just for this, I feel like I made the right choice by using this library.

While I'm not at all surprised that Bitbucket finally is purging #Mercurial, I'm still sad.

Someone in the #Mercurial IRC channel talking about the upcoming release and the corresponding release notes:

"it feels like jordi has provided half of the changes worth mentioning. the rest of us have just been goofing around :)"

Huh, Facebook vanished from #Mercurial development since sometime in October 2018. They're not in the mailing lists, the IRC channel, and they're certainly not sending patches anymore.

I wonder what's up? They've been threatening to fork off for a long while now. I bet they finally did it.

I, for one, am relieved to see them gone. They did some good stuff but they were also a little unpleasant to work with.

Huh, Facebook vanished from the #Mercurial development since sometime in October 2018. They're not in the mailing lists, the IRC channel, and they're certainly not sending patches anymore.

I wonder what's up? They've been threatening to fork off for a long while now. I bet they finally did it.

I, for one, am relieved to see them gone. They did some good stuff but they were also a little unpleasant to work with.

On April 5-7, there's going to be a #Mercurial sprint in #Japan. I kind of wish I could go, but it does seem out of the question.

https://www.mercurial-scm.org/wiki/5.0sprint

«There is no theoretical reason you can’t maintain two histories—-e.g. when rebasing have a “rebase-merge” commit that has the hash of the other tree, and optionally keep that history around in the git repo. Then you could do a ‘git blame —orig’ or whatever to switch between immutable and cleaned up history.

No VCS I’m aware of supports this. But they COULD.»

https://news.ycombinator.com/item?id=19007489

Friend, let me introduce you to #Mercurial #Evolve...

https://youtu.be/4OlDm3akbqg?t=840

This is great news: @sir's sr.ht has grown #Mercurial support. I am so happy about this.

https://man.sr.ht/hg.sr.ht/

This has been a week of lots of good news for me.

omfg I'm so happy. #Mercurial has word #diff #highlighting

I just accidentally deleted all top-level files from my project's .hg/ directory. I fat-fingered `rm foo *` when I meant to do `grep foo *`

However, #Mercurial seems to have been able to recreate and rebuild everything after I pulled from the remote git repo.

Nice! That's pretty resilient.

Hey, coders, programmers, hackers:

How many of you *don't* enjoy using #git or #mercurial or #svn or any kind of source control at all? I want to find people who just don't like it and wish there was a better way. I know you're out there!

Cool, #Mercurial is getting close to being #Python 3 ready:

https://tamytro.org/tmp/MercurialPy3.html

well, the #evolve extension for #mercurial does indeed work. In Totally Unrelated matters, the D in DVCS is useful.

trying out #mercurial changeset evolution with my blog's repo.