git

Back Open Paginator
04.11.2025 16:30
boltless (@boltless@hackers.pub)

mega-merge workflow를 사용하고 있는데 아주 사용감이 좋습니다. 사진은 9개의 다른 커밋 히스토리가 한번에 임시 머지되어 있는 모습

#git #jj-vcs





Show Original Post


04.11.2025 16:15
post (@post@programming.dev)

Pull Request Templates

programming.dev/post/40197454




Show Original Post


04.11.2025 12:55
giacomo (@giacomo@snac.tesio.it)
@mtorchiano@mastodon.uno

#Fossil has way more feature than #git, so much you need a separated forge to fill the gaps a little.

Yet, if you compare fossil and git, the former is way smaller than the latter.

So fossil is both simpler and more featureful, while still looking less "modern" because it clashes with the industrial aestetics of the day.

To me, being able to actually read and modify its source code without being overwhelmed by its complexity turns it to a convivial technology: it's not built to reduce users' and developers' degrees of freedom either through standardization or ui/ux, but to enable them to adapt it to their needs, actually increasing their degree of #freedom.

I think the tension here is rougly the same I see between #C (and #hare) and #Rust, between #Make and #Ninja, between #TinyCC and #LLVM (or #GCC), between #GTK2 and #GTK4, between #SysV and #systemd, between #BSD (or #9front) and #Linux and so on.

Due to the constraints of their age, some older tools are inheritally more suitable to build convivial technologies than other.

Corporations need to alienate their workers, to reduce their degree of freedom, to make them easy to replace. It's not just power play: it's somewhat intrinsic into the need to sell (and thus produce) standardized products that can appeal to many (and thus provide large profits) instead of creating custom solutions for the exact issue at hand that may be orginal, beautiful and tuned to the specific aestetics and goals of a specific (and maybe small) group of people... but need care, access rules and, in general, a community.

Software complexity only really serve industial (maybe militar-industrial) needs.
More often than not, against users.
Always against #developers.

The number of browsers shrinked after #Google launched #Chrome and lured #Mozilla to destroy #Firefox credibility, because a handful of corporations control #WHATWG (and #W3C). #HTML5 requires an overcomplicated #JS engine and #CSS got variables and calc and so on...
And don't even get me start about systemd. Or Linux's 500+ system calls.

C sucks in many ways but there are tons of compilers. Rust looks so "safe" (and is so hyped) that people rewrite working software with it (under permissive licensings that only benefit corporate interests) causing DoS in the wild. And nobody give a shit about the big picture that such incident shows!

But that's the fact with capitalism: it requires deep cultural homologation and submission, so that most people push in the "right" direction by themselves. They may vote differently, dress differently, care about different value but they all need to accept the basic assumptions that enable profit maximization.

Such push to complexity and homologation was lower decades ago because computers were slow and the field was still new.
Thus we got pearls like #forth, #Lisp, #Pascal/#Oberon and so on... even Linux, back in the early 2000 was a convivial technology designed more for people's (developers are still people) needs than for corporate needs.

Now Fossil is in fact modern technology, but it's built on a shitty language (with tons of implementations) that caps its complexity. And I think this is a sort of long term warranty about its usability in convivial contexts.

(sorry for the long reply... grow out of control... I guess this is something I was reasoning about since ages but never had an occasion to formulate...)



Show Original Post


04.11.2025 11:59
neil (@neil@mastodon.neilzone.co.uk)

# "Using LibreOffice and other Free software for documents as a lawyer"

I was asked recently about how I get on using LibreOffice for document-related legal work, and I promised to write down some thoughts.

The short answer is that I use a mix of LibreOffice and other FOSS tools, and I’m very positive about it, with no particular concerns.

If you have questions, please do ask!

neilzone.co.uk/2025/11/using-l

#LibreOffice #Linux #FOSS #lawfedi #vim #git #Markdown




Show Original Post


04.11.2025 10:36
lig (@lig@fosstodon.org)

No more custom scripts 🎉

git-wok now handles all your repo pushes in one go — no more juggling multiple terminals or half-baked automation.

Beta 8 is out now, and it’s almost perfect 🙂
👉 git-wok.dev/getting-started/

#GitWok #Git #CLI #DevTools #Automation





Show Original Post


04.11.2025 08:06
ct_Magazin (@ct_Magazin@social.heise.de)

Last Call: Effiziente Workflows für stabile Software im c't-Workshop entwickeln

Builds, Tests und Deployments automatisieren: Der Workshop "CI/CD mit GitLab" zeigt, wie Sie den gesamten Softwareprozess in einer Instanz effizient steuern.

heise.de/news/Last-Call-Effizi

#ContinuousDelivery #ContinuousIntegration #Git #IT #Softwareentwicklung #news




Show Original Post


04.11.2025 06:42
post (@post@programming.dev)

Serie: A rich git commit graph in your terminal

programming.dev/post/40179374




Show Original Post


04.11.2025 01:32
felipe (@felipe@bloom.surf)

SourceGit
felipe.lavin.blog/2025/11/03/s

SourceGit is an excellent graphical client for git; it helps navigate commits by timeline, filter by file, etc.

#git




Show Original Post


03.11.2025 22:43
unixbhaskar (@unixbhaskar@mastodon.social)

youtu.be/1GVoHtZjGlw




Show Original Post


03.11.2025 22:43
unixbhaskar (@unixbhaskar@fosstodon.org)

youtu.be/1GVoHtZjGlw

#linuxadmin #git #emacs #magit #opensource #tool




Show Original Post


03.11.2025 18:49
mjd (@mjd@mathstodon.xyz)

GIT ROT, n. When your topic branch has lived so long without being merged to the mainline that might be easier to start over than it would be to resolve the merge conflicts.

#git




Show Original Post


03.11.2025 18:01
lig (@lig@fosstodon.org)

🧑🏻‍💻 Been testing git-wok beta 6 for a few days now and honestly, it’s been rock solid. No major issues, just smooth handling of multi-repo workflows.

If you haven’t seen it yet, git-wok makes it easy to manage multiple Git repositories at once, a bit like how Cargo or npm manage packages.
Your `wok.toml` defines the workspace, while committed submodule objects act as a lock file capturing exact repo states.

Give it a try 👉 git-wok.dev/getting-started

#GitWok #Git #OpenSource #DevTools




Show Original Post


1 ...205 206 207 208 209 210 211 212 213 214 215 ...348
UP