←back to thread

Mozilla Firefox – Official GitHub repo

(github.com)
848 points thefilmore | 3 comments | 13 May 25 05:23 UTC | HN request time: 0.621s | source
Show context
CorrectHorseBat ◴[13 May 25 05:48 UTC] No.43969915[source]▶
So they moved from hg to git? Or is this just an official mirror
replies(2): >>43969921 #>>43970007 #
shit_game ◴[13 May 25 05:49 UTC] No.43969921[source]▶
firefox development has been moved from mercurial to git since early november of 2023

https://www.phoronix.com/news/Firefox-Going-Git

replies(1): >>43969989 #
swiftcoder ◴[13 May 25 06:05 UTC] No.43969989[source]▶
Interesting that their issues are blamed on "dual SCM", not on Mercurial itself. I guess just the weight of contributors expecting Git as the default is sinking the big Mercurial projects these days.
replies(2): >>43970215 #>>43970217 #
dgoldstein0 ◴[13 May 25 06:52 UTC] No.43970215[source]▶
Isn't mercurial abandonware? Or maybe I'm just remembering that gitlab dropped support. If it's not dead yet seems to be getting there
replies(2): >>43970570 #>>43970843 #
1. swiftcoder ◴[13 May 25 08:42 UTC] No.43970843[source]▶
It’s still used by Meta, at any rate (albeit a very scaled version thereof). Meta picked it for their monorepo when Linus wasn’t willing to play ball on extending Git for their use case.
replies(1): >>43970853 #
2. arp242 ◴[13 May 25 08:43 UTC] No.43970853[source]▶
Is it still used there? I know they did in the past, but reading up a bit on the background on all of this I found https://github.com/facebook/sapling, and it seems that's what they're using now?
replies(1): >>43982736 #
3. swiftcoder ◴[14 May 25 10:03 UTC] No.43982736[source]▶
I don't know for sure today, but Sapling was mercurial-compatible, at least early in development.