#dvcs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dvcs, aggregated by home.social.
-
Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:
Privacy and Security #privsec
Search
Data & hosting
publishing code
switching browsers
Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)
all of the above, in other words: #Disenshittification
#Versioning (#DVCS) & #Archiving & #Publishing
Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)
-
Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:
Privacy and Security #privsec
Search
Data & hosting
publishing code
switching browsers
Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)
all of the above, in other words: #Disenshittification
#Versioning (#DVCS) & #Archiving & #Publishing
Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)
-
Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:
Privacy and Security #privsec
Search
Data & hosting
publishing code
switching browsers
Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)
all of the above, in other words: #Disenshittification
#Versioning (#DVCS) & #Archiving & #Publishing
Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)
-
Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:
Privacy and Security #privsec
Search
Data & hosting
publishing code
switching browsers
Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)
all of the above, in other words: #Disenshittification
#Versioning (#DVCS) & #Archiving & #Publishing
Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)
-
Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:
Privacy and Security #privsec
Search
Data & hosting
publishing code
switching browsers
Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)
all of the above, in other words: #Disenshittification
#Versioning (#DVCS) & #Archiving & #Publishing
Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)
-
#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git -
#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git -
#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git -
#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git -
#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git -
I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.
However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.
Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).
I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:
#BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo
-
I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.
However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.
Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).
I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:
#BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo
-
I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.
However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.
Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).
I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:
#BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo
-
I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.
However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.
Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).
I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:
#BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo
-
I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.
However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.
Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).
I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:
#BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo
-
#Git 2.51.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.51.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.51.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
Jujitsu? I'm going to learn Jujitsu?
#git #DVCS
https://steveklabnik.github.io/jujutsu-tutorial/ -
Jujitsu? I'm going to learn Jujitsu?
#git #DVCS
https://steveklabnik.github.io/jujutsu-tutorial/ -
Jujitsu? I'm going to learn Jujitsu?
#git #DVCS
https://steveklabnik.github.io/jujutsu-tutorial/ -
Jujitsu? I'm going to learn Jujitsu?
#git #DVCS
https://steveklabnik.github.io/jujutsu-tutorial/ -
Jujitsu? I'm going to learn Jujitsu?
#git #DVCS
https://steveklabnik.github.io/jujutsu-tutorial/ -
git manpage generator: A parody, something generating plausible but fictional documentation for git
https://git-man-page-generator.lokaltog.net/#bWFzc2FnZSQkYmFyZSByZXBvc2l0b3J5
#documentation #funny #dvcs #unix #git #vcs #+ -
git manpage generator: A parody, something generating plausible but fictional documentation for git
https://git-man-page-generator.lokaltog.net/#bWFzc2FnZSQkYmFyZSByZXBvc2l0b3J5
#documentation #funny #dvcs #unix #git #vcs #+ -
git manpage generator: A parody, something generating plausible but fictional documentation for git
https://git-man-page-generator.lokaltog.net/#bWFzc2FnZSQkYmFyZSByZXBvc2l0b3J5
#documentation #funny #dvcs #unix #git #vcs #+ -
git manpage generator: A parody, something generating plausible but fictional documentation for git
https://git-man-page-generator.lokaltog.net/#bWFzc2FnZSQkYmFyZSByZXBvc2l0b3J5
#documentation #funny #dvcs #unix #git #vcs #+ -
git manpage generator: A parody, something generating plausible but fictional documentation for git
https://git-man-page-generator.lokaltog.net/#bWFzc2FnZSQkYmFyZSByZXBvc2l0b3J5
#documentation #funny #dvcs #unix #git #vcs #+ -
In other #DVCS news, Canonical is dropping Bazaar from Launchpad: https://www.omgubuntu.co.uk/2025/06/launchpad-bazaar-support-being-removed
"Canonical sunsetting Bazaar may seem abrupt given it’s the code versioning system it helped develop and continues to make use of for the day-to-day development of Ubuntu itself..."
I continue to scratch my head at the Bazaar fork called Breezy (mentioned near the top of that article). I can't see why it exists or why someone would choose it, but... it exists.
https://www.breezy-vcs.org/ -
In other #DVCS news, Canonical is dropping Bazaar from Launchpad: https://www.omgubuntu.co.uk/2025/06/launchpad-bazaar-support-being-removed
"Canonical sunsetting Bazaar may seem abrupt given it’s the code versioning system it helped develop and continues to make use of for the day-to-day development of Ubuntu itself..."
I continue to scratch my head at the Bazaar fork called Breezy (mentioned near the top of that article). I can't see why it exists or why someone would choose it, but... it exists.
https://www.breezy-vcs.org/ -
In other #DVCS news, Canonical is dropping Bazaar from Launchpad: https://www.omgubuntu.co.uk/2025/06/launchpad-bazaar-support-being-removed
"Canonical sunsetting Bazaar may seem abrupt given it’s the code versioning system it helped develop and continues to make use of for the day-to-day development of Ubuntu itself..."
I continue to scratch my head at the Bazaar fork called Breezy (mentioned near the top of that article). I can't see why it exists or why someone would choose it, but... it exists.
https://www.breezy-vcs.org/ -
In other #DVCS news, Canonical is dropping Bazaar from Launchpad: https://www.omgubuntu.co.uk/2025/06/launchpad-bazaar-support-being-removed
"Canonical sunsetting Bazaar may seem abrupt given it’s the code versioning system it helped develop and continues to make use of for the day-to-day development of Ubuntu itself..."
I continue to scratch my head at the Bazaar fork called Breezy (mentioned near the top of that article). I can't see why it exists or why someone would choose it, but... it exists.
https://www.breezy-vcs.org/ -
In other #DVCS news, Canonical is dropping Bazaar from Launchpad: https://www.omgubuntu.co.uk/2025/06/launchpad-bazaar-support-being-removed
"Canonical sunsetting Bazaar may seem abrupt given it’s the code versioning system it helped develop and continues to make use of for the day-to-day development of Ubuntu itself..."
I continue to scratch my head at the Bazaar fork called Breezy (mentioned near the top of that article). I can't see why it exists or why someone would choose it, but... it exists.
https://www.breezy-vcs.org/ -
#Git 2.50.1 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.50.1 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.50.1 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.49.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.49.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
#Git 2.49.0 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/
-
Somebody please enlighten me; I am genuinely curious about this.
I honestly do not understand why a Git-based collaboration tool would allow either only fast-forward merges in a repo or always force a merge commit, like GitLab does.
Is there any good reason for this?
Is there ever something wrong about "create a merge commit if it's not a fast-forward, and do a fast-forward merge otherwise" that I am missing?
-
Somebody please enlighten me; I am genuinely curious about this.
I honestly do not understand why a Git-based collaboration tool would allow either only fast-forward merges in a repo or always force a merge commit, like GitLab does.
Is there any good reason for this?
Is there ever something wrong about "create a merge commit if it's not a fast-forward, and do a fast-forward merge otherwise" that I am missing?
-
Somebody please enlighten me; I am genuinely curious about this.
I honestly do not understand why a Git-based collaboration tool would allow either only fast-forward merges in a repo or always force a merge commit, like GitLab does.
Is there any good reason for this?
Is there ever something wrong about "create a merge commit if it's not a fast-forward, and do a fast-forward merge otherwise" that I am missing?
-
Somebody please enlighten me; I am genuinely curious about this.
I honestly do not understand why a Git-based collaboration tool would allow either only fast-forward merges in a repo or always force a merge commit, like GitLab does.
Is there any good reason for this?
Is there ever something wrong about "create a merge commit if it's not a fast-forward, and do a fast-forward merge otherwise" that I am missing?
