#dvcs — Public Fediverse posts

@Hyperlynx why not? Anyone who says they like #Git surely must suffer from the Stockholm syndrome. And I don’t even to need to advocate for a specific alternative because every other common or semi-common #DVCS is usable. Git is not. Yet, to contribute to 99% of #FLOSS you have to suffer that pile of dogshit. So I don’t.

Hi All
Guide me please 😅
I'm using GitHub all these days to store files. I plan to move my files to open source platforms like codeberg,gitea etc. But I want a mirror of my codeberg like repo in GitHub etc, just as a backup.
2 ways I can think of:
1) Pushing to 2 remotes from my local
2) Mirroring one repo completely in another platform
Want ur opinion on these or any other methods I'm unaware of.
#git #jujutsu #jj #github #gitea #codeberg #forgejo #vcs #dvcs #repo

Ob es wirklich so eine gute Idee war, ein #DVCS #Fossil zu nennen, um ein positives Konnotat der Beständigkeit der Änderungen zu erreichen?

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:

https://codeberg.org/pygospa

#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/

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 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/

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?

#Git #GitLab #VCS #DVCS

#Git 2.49.0 RC1 has been released (#SCM / #SourceControlManagement / #SourceCodeManagement / #VCS / #VersionControl / #VersionControlSystem / #DVCS / #DistributedVersionControlSystem / #DistributedVersionControl) https://git-scm.com/

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/