Notices tagged with mercurial
-
#Mercurial #Paris conference postponed to early 2023: https://mercurial.paris/posts/2022/09/09/mercurial-paris-2022-postponed/
-
#Mercurial #Paris Conference: Wednesday 21 to Friday 23 of September: https://mercurial.paris/events/mercurial-conference-paris-2022/
-
"Initially, a lot of developers were skeptical about #Mercurial and preferred #Git," Szorc said. "Now, apparently a number of their developers have forgot how to use Git." https://www.theregister.com/2016/10/18/facebook_mercurial_devs_forget_git/
-
"Initially, a lot of developers were skeptical about #Mercurial and preferred #Git," Szorc said. "Now, apparently a number of their developers have forgot how to use Git."
-
#Mercurial's journey to #Python 3: https://gregoryszorc.com/blog/2020/01/13/mercurial's-journey-to-and-reflections-on-python-3/
-
I think y’all know I favor the #Fossil #SCM / #DVCS over #Git (though I’m giving #Mercurial ( #Hg ) another look as well. I’m resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
-
#Mercurial now supports !Python 3. With years of work ahead to fix the inevitable bugs. https://gregoryszorc.com/blog/2020/01/13/mercural%27s-journey-to-and-reflections-on-python-3/ #hg #py3
#Breezy, #brz, ( the continuation of #Bazaar, #bzr, ) also supports #Python3 https://pypi.org/project/breezy/
-
Planning to play with #Kallithea https://kallithea-scm.org/ soon. I’m still very much in favor of #Fossil https://fossil-scm.org/home/doc/trunk/www/index.wiki but I’m not rigid about it (the way many #Git and #Github users are). If either Git or #Mercurial ( #Hg ) https://www.mercurial-scm.org/ are appropriate for the situation, I’ll use them.
-
Bitbucket plans to delete all #Mercurial repos tomorrow. I clone all to a backup and kiss them goodbye. On to https://hg.sr.ht/~arnebab !
-
#Git users discuss renaming the default branch from "master" to "main" or "principal" or similar. #Mercurial users stay with "default". https://dev.to/damcosset/replacing-master-in-git-2jim
-
Using #ediff3 from #Emacs as merge-tool in #Mercurial (hg): https://www.draketo.de/software/mercurial-ediff3-emacs.html
-
The golden rule of rebasing ( https://www.atlassian.com/git/tutorials/merging-vs-rebasing#the-golden-rule-of-rebasing ) is a symptom of deficiencies in #Git that are resolved in #Mercurial with the evolve extension: https://blog.disy.net/hg-evolution/
-
Automatic coordinated rebase with changeset #evolution and #Mercurial: https://blog.disy.net/hg-evolution/ #hg #scm #vcs !fs
-
A complete #Mercurial branching strategy: https://www.draketo.de/software/mercurial-branching-strategy — new design, with #PDF via #Emacs #orgmode https://www.draketo.de/software/mercurial-branching-strategy.pdf
-
!hg bundle -t zstd-v2 --config experimental.bundlecomplevel=22 --all full-history-tiny.bundle #mercurial #vcs #versioncontrol
-
Update your #mercurial repo workdir automatically when you push from home-office: [hooks] changegroup.update = hg update #hg
-
The #Mercurial evolve user guide really shaped up: https://www.mercurial-scm.org/doc/evolution/user-guide.html collaborative history editing
-
#Mercurial 5.0 comes with support for #Python3 (in β) → https://www.mercurial-scm.org/wiki/Release5.0 #python
-
"if you've got a big-repo problem (Google, …) #Mercurial will work for you today,… #git will require significant…investment" — Augie Fackler