rrwo (@rrwo@floss.social)
I'm getting "Segmentation fault (core dumped)" errors from #git when using `git add -p`
How is your morning going?
Show Original Post
berkes (@berkes@mastodon.nl)
Another 23 minutes of "TIL🤯 why did I only learn this now"
So You Think You Know #Git Part 2 - by Scott Chacon.
https://youtube.com/watch?v=Md44rcw13k4&si=dPWbAhoB9ucziJlZ
Show Original Post
macberg (@macberg@mastodon.online)
#Obsidian users, what's the benefits (and drawbacks) of using #git instead of #SyncThing?
Show Original Post
kernellogger (@kernellogger@fosstodon.org)
/me wonders why #Git supports
$ git remote set-branches remote_bar --add branch_foo
but not an equivalent like
$ git remote set-branches remote_bar --remove branch_foo
/me assumes the answer is the usual "nobody cared enough to implement it yet"
/me goes an removes the relevant line from .git/config manually
Show Original Post
todd_a_jacobs (@todd_a_jacobs@infosec.exchange)
I deeply respect @briankrebs, but in this case I think the data he's presenting is fundamentally invalid. A little-known fact about #Git history is that #timestamps are both definable and mutable. While you might be able to make statements about when a Git commit was pushed to a server using the server-side SSH or HTTP logs, the fact that you can set GIT_AUTHOR_DATE and GIT_COMMITTER_DATE as environment variables means you can't rely on commit timestamps alone for this type of analysis.
This is a feature of Git since the ability to squash or rewrite its mutable history is a key differentiator compared to #FossilSCM or other #SCMs that treat history as immutable(ish). For example, allowing one to do things like report a commit as the time a patch or source document was originally written rather than just noting when it was committed or merged can be very useful in accurately representing the real-world evolution of data created outside the repository.
This is not a flaw in Git. Anyone savvy enough to craft the #xz attack could just as easily have adjusted their system clocks instead, leading to fraudulent timestamps in the commit history anyway.
Forensically, you'd need to look at the timestamps from NTP-backed server or router logs, not just the Git history. All Git clients are technically "offline" until they push one or more commits to a remote, so there's really no way to validate client-side SCM timestamps. This is also true of email headers, filesystem attributes, and any other data that relies on real system clocks or user-defined timestamps, so you'd need more points of correlation than are provided here.
Show Original Post
TeXUsersGroup (@TeXUsersGroup@techhub.social)
From #CTAN:
Erik Nijenhuis submitted an update to the gitinfo-lua package.
Version: 1.0.3
License: lppl1.3c
Summary description: Display git project information in your LaTeX projects
https://www.ctan.org/pkg/gitinfo-lua
Show Original Post
soupglasses (@soupglasses@hachyderm.io)
If you found a #Git repository you like, which forges would you give the equivalent of a star on?
(Please retoot 
)
Show Original Post
epompeii (@epompeii@mastodon.social)
🐰 Bencher v0.4.5 Released! 🎉
Important Update: Bencher can now track #git rebases and base/target branch changes!
See the updated and expanded branch selection docs for more details on how to upgrade your #ContinuousBenchmarking setup: https://bencher.dev/docs/explanation/branch-selection/
Show Original Post
mmarif (@mmarif@mastodon.social)
GitNex 5.4.0 is out with import/export app data and more:
- Delete email from account
- Update profile settings
- Add SSH key to account
Read release notes for more: https://codeberg.org/gitnex/GitNex/releases
Release post on: https://najigram.com/category/gitnex
#gitnex #codeberg #forgejo #gitea #git #android #app
Show Original Post
lemor (@lemor@mastodon.social)
A convenient way to manage your dots through git
Show Original Post
parpok (@parpok@101010.pl)
nie rozumiem o co chodzi z tym "Projects that value your Privacy" i gitea jako "Mostly"
bo jedyne co widzę to to że "my z forgejo jesteśmy FOSS non profit więc jesteśmy lepsi od tych otwartych z planami dla enterprise czy zamkniętymi"
#FOSS #Gitea #Forgejo #Privacy #git
Show Original Post
pesche (@pesche@mastodon.green)
Ever committed to your #git repo with the wrong email address, because you have different addresses for corporate and open source work?
@alexandre has you covered, using #includeIf in your git config : https://blog.touret.info/2024/04/02/git_profiles_at_once/
Show Original Post