#mercurial — Public Fediverse posts

Would love to tinker around with #mercurial is there a alternative to #cgit which can do #hg?

Не Git-ом единым: гид по системам контроля версий для особых случаев

А есть ли жизнь вне GIT? Что там? Может там летают птеродактили или НЛО? Или там просто пустое поле? Давайте разбираться.

https://habr.com/ru/articles/984556/

#Git #Mercurial #Subversion #Perforce #Darcs #Pijul

Alors oui, #git (et tout autre gestionnaire de versions) est un outil absolument extraordinaire et on aurait beaucoup de mal à faire notre travail de #dev sans ça !

Et j'en ai utilisé quelques uns : #CVS 😄 , #SVN, #Bazaar, #Mercurial

Maintenant... quand tu vois que, sur un projet #python, le dossier .git (qui contient l'historique des modifications) représente... 87% du poids total du machin... 😱

My FOSS laws:

1. You can ask, but not demand.
2. You can help, but not enforce.
3. You can critic, but not rant.
4. You can compare, but not disparage.
5. You can compete, but not sabotage.

That should be the guidelines for any FOSS discussion.

#FOSS #Free #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #Subversion #Versioning #Git #GitHub #GitLab #Mercurial #OSS #SoftwareDevelopment #GNU #MIT

My FOSS laws:

1. You can ask, but not demand.
2. You can help, but not enforce.
3. You can critic, but not rant.
4. You can compare, but not disparage.
5. You can compete, but not sabotage.

That should be the guidelines for any FOSS discussion.

#FOSS #Free #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #Subversion #Versioning #Git #GitHub #GitLab #Mercurial #OSS #SoftwareDevelopment #GNU #MIT

My FOSS laws:

1. You can ask, but not demand.
2. You can help, but not enforce.
3. You can critic, but not rant.
4. You can compare, but not disparage.
5. You can compete, but not sabotage.

That should be the guidelines for any FOSS discussion.

#FOSS #Free #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #Subversion #Versioning #Git #GitHub #GitLab #Mercurial #OSS #SoftwareDevelopment #GNU #MIT

My FOSS laws:

1. You can ask, but not demand.
2. You can help, but not enforce.
3. You can critic, but not rant.
4. You can compare, but not disparage.
5. You can compete, but not sabotage.

That should be the guidelines for any FOSS discussion.

#FOSS #Free #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #Subversion #Versioning #Git #GitHub #GitLab #Mercurial #OSS #SoftwareDevelopment #GNU #MIT

My FOSS laws:

1. You can ask, but not demand.
2. You can help, but not enforce.
3. You can critic, but not rant.
4. You can compare, but not disparage.
5. You can compete, but not sabotage.

That should be the guidelines for any FOSS discussion.

#FOSS #Free #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #Subversion #Versioning #Git #GitHub #GitLab #Mercurial #OSS #SoftwareDevelopment #GNU #MIT

I've created a stripped-down template for hgweb so that I can still link to the latest version of files, but not any others 🙂

For example: https://dev.ibboard.co.uk/repos/other/Puppet/file/tip/modules/website/files/greatfirewallagainstchina.conf

#Mercurial #Apache2 #SpamBots #ScraperBots #SysAdminProblems

I've created a stripped-down template for hgweb so that I can still link to the latest version of files, but not any others 🙂

For example: https://dev.ibboard.co.uk/repos/other/Puppet/file/tip/modules/website/files/greatfirewallagainstchina.conf

#Mercurial #Apache2 #SpamBots #ScraperBots #SysAdminProblems

I've created a stripped-down template for hgweb so that I can still link to the latest version of files, but not any others 🙂

For example: https://dev.ibboard.co.uk/repos/other/Puppet/file/tip/modules/website/files/greatfirewallagainstchina.conf

#Mercurial #Apache2 #SpamBots #ScraperBots #SysAdminProblems

I've created a stripped-down template for hgweb so that I can still link to the latest version of files, but not any others 🙂

For example: https://dev.ibboard.co.uk/repos/other/Puppet/file/tip/modules/website/files/greatfirewallagainstchina.conf

#Mercurial #Apache2 #SpamBots #ScraperBots #SysAdminProblems

I've created a stripped-down template for hgweb so that I can still link to the latest version of files, but not any others 🙂

For example: https://dev.ibboard.co.uk/repos/other/Puppet/file/tip/modules/website/files/greatfirewallagainstchina.conf

#Mercurial #Apache2 #SpamBots #ScraperBots #SysAdminProblems

https://blog.gslin.org/archives/2025/05/14/12393/mozilla-%e6%8a%8a-firefox-%e7%9a%84-code-repository-%e6%90%ac%e5%88%b0-github-%e4%b8%8a/

Mozilla 把 Firefox 的 code repository 搬到 GitHub 上

#browser #code #firefox #git #github #hg #mercurial #mozilla #source

I nowadays get the same uncomfortable feeling when engaging with #GitHub that I used to get when dealing with #Google. Maybe I'll soon reach the point where seeing someone use GitHub is as much of a culture shock as spotting someone searching with Google is to me today 💥

Hopefully all the projects I'm interested in would have moved on by then :forgejo:

#Forgejo #Git #CultureShock #SelfHosting #Codeberg #Mercurial

Mercurial 也有接 Git 的 Plugin

前幾天在 Lobsters 上看到的：「mercurial / hg-git」。 看到才想到，既然 Git 這邊有 git-hg 這樣的工具 (而且有不同的人開發不同的版本) 讓 Git 使用者可以操作 Mercurial repository，反過來當然在 Mercurial 這邊也會有 hg-git 這樣的工具。 不同的是 Git 這邊有好幾套，沒有「官方」版本 (不過 git-svn 算是官方維護？)，而 Mercurial 這邊的 hg-git 算是官方在維護的。 算是個有趣的小知識 (?)。 …

https://blog.gslin.org/archives/2025/04/10/12337/mercurial-%e4%b9%9f%e6%9c%89%e6%8e%a5-git-%e7%9a%84-plugin/

#git #hg #mercurial #plugin #repository

Evolve 11.1.8 and topic 1.1.8 are out!

This is a bugfix release. The most notable change is the compatibility with Mercurial 7.0rc0 and the upcoming Mercurial 7.0. The files on PyPI were also produced by the newest available build frontend and they now include a binary distribution (wheel). We didn't provide wheels for hg-evolve before (AFAIR), so if there any issues, please let us know.

https://marc.info/?l=mercurial&m=174178070510085&w=2

#hg #mercurial

Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

https://www.mercurial-scm.org/

Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

https://www.mercurial-scm.org/

Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

https://www.mercurial-scm.org/

Everyone excited with #jujutsu. But I do think #sapling has a lot of polish. A fork of #mercurial, with lots of usability thoughts. 😎 And fully #git compatible as well.

Of course, if you want the real MVP, mercurial is still around. All with the design of using a #DVCS that makes sense. 😁

https://www.mercurial-scm.org/

Evolve 11.1.7 and topic 1.1.7 are out!

As well as 11.1.7.post1 and 1.1.7.post1 versions that fix a silly packaging mistake (oops :blobcatMelt2: ) and provide packages on PyPI that were packaged with newer tools.

There are no significant changes between the versions if you install from source or use TortoiseHG, for example.

So if you use PyPI, please install the latest .post1 versions, otherwise don't worry, you can use 11.1.7 and 1.1.7 if you want.

#hg #mercurial

Evolve 11.1.7 and topic 1.1.7 are out!

This is a special bugfix release that includes one feature from default
branch. Now ``obslog --patch`` can show patches for changesets that were
rebased. Since this feature uses in-memory rebase, it requires Mercurial
5.6 or newer, where it is fully supported. Also a version check that was
failing on Mercurial 6.8 was fixed (minor releases like 6.8.1 weren't
affected).

https://marc.info/?l=mercurial&m=173901684125097&w=2

The next toot describes .post1 version.

#hg #mercurial

As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible

As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible

As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible

As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible

As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible

As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

#svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

Added a fallback for #infocalypse push: if a repository has fallen out, #hg fn-push will automatically re-create it (if you have the private key):

https://hg.sr.ht/~arnebab/infocalypse
https://github.com/hyphanet/infocalypse
USK@6~ZDYdvAgMoUfG6M5Kwi7SQqyS-gTcyFeaNN1Pf3FvY,OSOT4OEeg4xyYnwcGECZUX6~lnmYrZsz05Km7G7bvOQ,AQACAAE/infocalypse.R1/34
https://wiki.mercurial-scm.org/Infocalypse
https://www.draketo.de/english/freenet/real-life-infocalypse

#mercurial #decentralized #dvcs #privacy

Added a fallback for #infocalypse push: if a repository has fallen out, #hg fn-push will automatically re-create it (if you have the private key):

https://hg.sr.ht/~arnebab/infocalypse
https://github.com/hyphanet/infocalypse
USK@6~ZDYdvAgMoUfG6M5Kwi7SQqyS-gTcyFeaNN1Pf3FvY,OSOT4OEeg4xyYnwcGECZUX6~lnmYrZsz05Km7G7bvOQ,AQACAAE/infocalypse.R1/34
https://wiki.mercurial-scm.org/Infocalypse
https://www.draketo.de/english/freenet/real-life-infocalypse

#mercurial #decentralized #dvcs #privacy

Added a fallback for #infocalypse push: if a repository has fallen out, #hg fn-push will automatically re-create it (if you have the private key):

https://hg.sr.ht/~arnebab/infocalypse
https://github.com/hyphanet/infocalypse
USK@6~ZDYdvAgMoUfG6M5Kwi7SQqyS-gTcyFeaNN1Pf3FvY,OSOT4OEeg4xyYnwcGECZUX6~lnmYrZsz05Km7G7bvOQ,AQACAAE/infocalypse.R1/34
https://wiki.mercurial-scm.org/Infocalypse
https://www.draketo.de/english/freenet/real-life-infocalypse

#mercurial #decentralized #dvcs #privacy

Added a fallback for #infocalypse push: if a repository has fallen out, #hg fn-push will automatically re-create it (if you have the private key):

https://hg.sr.ht/~arnebab/infocalypse
https://github.com/hyphanet/infocalypse
USK@6~ZDYdvAgMoUfG6M5Kwi7SQqyS-gTcyFeaNN1Pf3FvY,OSOT4OEeg4xyYnwcGECZUX6~lnmYrZsz05Km7G7bvOQ,AQACAAE/infocalypse.R1/34
https://wiki.mercurial-scm.org/Infocalypse
https://www.draketo.de/english/freenet/real-life-infocalypse

#mercurial #decentralized #dvcs #privacy

Added a fallback for #infocalypse push: if a repository has fallen out, #hg fn-push will automatically re-create it (if you have the private key):

https://hg.sr.ht/~arnebab/infocalypse
https://github.com/hyphanet/infocalypse
USK@6~ZDYdvAgMoUfG6M5Kwi7SQqyS-gTcyFeaNN1Pf3FvY,OSOT4OEeg4xyYnwcGECZUX6~lnmYrZsz05Km7G7bvOQ,AQACAAE/infocalypse.R1/34
https://wiki.mercurial-scm.org/Infocalypse
https://www.draketo.de/english/freenet/real-life-infocalypse

#mercurial #decentralized #dvcs #privacy

Evolve 11.1.6 and topic 1.1.6 are out!

This is a bugfix release that addresses a few bugs in both extensions related to: content-divergence of splits, obshashrange cache, internal topic stack implementation (used in e.g. `hg topics` command). The full release notes don't fit into a single toot, but are, as usual, available on the mailing list:

https://marc.info/?l=mercurial&m=173280547932588&w=2

#hg #mercurial

Mercurial 6.8.2 is out!

As usual, there are various bugfixes in this stable release, but one thing is especially worth mentioning: this is planned to be the last version that supports Python 3.6 and 3.7. At the same time, Python support was extended to 3.13.

A short overview of changes: https://wiki.mercurial-scm.org/Release6.8

#hg #mercurial

Evolve 11.1.5 and topic 1.1.5 are out!

A minor release that's aimed at being compatible with the soon-to-be released Mercurial 6.9, but there are some small changes too:

https://marc.info/?l=mercurial&m=172995615320877&w=2

#hg #mercurial

AFAICT, #Facebook / #Meta uses a #Mercurial-inspired #VersionControl system named #Sapling (https://sapling-scm.com/):

“Why Facebook Doesn’t Use Git”, Graphite (https://graphite.dev/blog/why-facebook-doesnt-use-git).

On HN: https://news.ycombinator.com/item?id=39635936

On Lobsters: https://lobste.rs/s/r9lewl/why_facebook_doesn_t_use_git

#Git #MonoRepo

I’ve been made aware of the outage over on Sourcehut. The main crew (Drew, Simon, and Conrad) are restoring the main services. I’m looking at the mercurial hosting right now. More info here. #srht #mercurial https://outage.sr.ht/

So I think that the visitor WiFi at #WarHammerWorld blocks SSH connections which means I have to tether to my phone to use #hg / #mercurial (or #git)

#Git always had from the beginning very serious workflow flaws.
After years, #git-extra #gitflow, and many other #CLI tools appeared without so much success.
#TUI tools like #lazygit, #gitui and #tig reduced rightly the friction, but the complexity of use is still here when you close them.

#jujutsu is a new alternative interface to Git #CLI written in #rust taking the best from #Mercurial #Darcs #Pijul and of course #Git

https://github.com/martinvonz/jj#introduction
https://github.com/martinvonz/jj/blob/main/docs/git-comparison.md#overview

Just found out about #gitops with #elixir called #pluralsh.

Going to have to check it out. Though downside is they only have support for #github and #gitlab. ⚰️ Neither which I use for my personal #codeforge. However! They plan to support #mercurial! 🤯 That alone makes the software worth a glance or three for me. 😭

https://www.plural.sh/

@schmidt_fu @drisc
Inside the #FreenetProject there's the possibility to share #Mercurial repositories decentral & anonym.

/cc @ArneBab

@frankiesaxx yeah, I think that if they should up at your door, you probably *can* call them a #grammarNazi 😂

Thanks for your feedback. :)

I think it all is a good argument to have your content publicly available under some kind of #versionControlSystem such as for instance #git, #bzr or #mercurial, so people can just submit patches.

I guess what we're missing is easy front ends for less tech-savvy contributers, especially in the form of plugins for #wordpress and #blogger.