'"[…] introduces preliminary support for a new reference storage backend called “reftable,” promising faster lookups, reads, and writes for repositories with any number of references. […]
Preliminary support for SHA-1 and SHA-256 interoperability
[…] git config learned a new option to help document your .gitconfig file […]"'
why does #git when pushing to a remote helper, first "list" the remote, then send the helper a "push", and only then notice if there's a non-fast-forward and claim the push has failed?
This seems to mean every remote helper has to detect non-fast-forward pushes and reject them, redundantly to git's own detection of the same thing.
(See for example git-remote-gcrypt documenting this as "A longstanding bug is that every git push effectively has a --force.")
I can’t get over how cool it is to view my posts from any server. I’m definitely going to use activitypub for my social media I’m planning on making. I was going to use @Discourse , but considering it’s like #GitLab where you are only able to self host and each instance of discourse can’t interconnect makes me kinda sad. But activitypub seems like the only way I feel happy in both ways.
BTW, we went "the hard way" and picked the sourcehut todo service as a bug tracker and project management tool for RDE, Ares, Arei and neighboring projects.
It's very bare-bone, but we could implement cross-project milestones via labels, it's already have basic filtering and searching and integrates nicely with email and git.
Will be developing the rest of the functionality as we go. Probably via API or by upstreaming patches to sourcehut.
#sxmo#linuxmobile news:
i fixed the wifi-sec hotspot creation bug, added a 'GSM Disable' entry and a 'Wifi Credentials' to show pw in text and qr-code of the connected wifi or hotspot.
and:
i decided to stop messing with sourcehut, #git send-email and upstream, for fuck sake, its so demotivating! to which email address? why did it not only send the last commit? where is it gone?
i prefer to use my time for features/fixes and to document them, not to messup pipelines of others....
Kennt ihr #Git? Auch wenn ihr kein(e) Programmierer:in seid, dann seid ihr bestimmt schonmal auf #GitHub, #GitLab o.Ä. gestoßen. Auch als Designer:in, Maker:in, Texter:in oder einfach nur zum Projektmanagement spielen Git und die dazugehörigen Plattformen heute eine große Rolle. Wir erklären Git/GitHub/GitLab für Nicht-Programmierer in einem dreistündigen Workshop am Sonntag, den 19. Mai. https://www.welcome-werkstatt.de/veranstaltungen/git-fuer-nicht-programmierer
PSA: Do not submit "omnibus" pull requests to #git repos, especially without talking to the maintainer first. Keeping PRs generally focused to one particular problem or feature makes things far more manageable for reviewing, testing, and reverting/bug-fixing later on. I would always much rather have 10 smaller PRs focused one specific thing each than one massive unsolicited one with a bunch of scope creep.
It's a big mix of small and medium-sized changes:
– A spiffy new welcome window, with recent repos
– You can now open a special example repository for testing things, that resets when you close its window. Go nuts!
– Check the global Git config using the sensibly-formatted table in Settings.
– Never forget about a rebase again: Retcon shows a big obvious badge in the Dock whenever you're paused for editing.