Rainer Gerhards
@rainergrf.mastodon.social.ap.brid.gy
rsyslog lead develooper. European. Security-Aware. Serving as councilman in the village of Großrinderfeld.
*Don't fear AI more than NS (natural stupidity).*
🌉 bridged from https://mastodon.social/@rainergrf on the fediverse by https://fed.brid.gy/
*Don't fear AI more than NS (natural stupidity).*
🌉 bridged from https://mastodon.social/@rainergrf on the fediverse by https://fed.brid.gy/
@ArneBab Yeah, but for the public project, I cannot enforce this. Even after a fork, all info should be available (I do not like lock-in).
September 6, 2025 at 4:31 PM
@ArneBab Yeah, but for the public project, I cannot enforce this. Even after a fork, all info should be available (I do not like lock-in).
@ArneBab one final try today : issue number: I have seen too many services like GitHub come and go (even ones like sourceforge that everyone considered to stay forever as place to go to). Commit message must be self explanatory without any external service. For ease of reference, we put full url […]
Original post on mastodon.social
mastodon.social
September 1, 2025 at 7:20 PM
@ArneBab one final try today : issue number: I have seen too many services like GitHub come and go (even ones like sourceforge that everyone considered to stay forever as place to go to). Commit message must be self explanatory without any external service. For ease of reference, we put full url […]
@ArneBab one "to" too much 😉. I mean that each commit must leave the code in a working state... Ah, and I seem to have been tired (long meetings), "git bisect" I meant. But I guess that's it for today, I've seen too many typos in this message already.
September 1, 2025 at 7:12 PM
@ArneBab one "to" too much 😉. I mean that each commit must leave the code in a working state... Ah, and I seem to have been tired (long meetings), "git bisect" I meant. But I guess that's it for today, I've seen too many typos in this message already.
@ArneBab there is need to to break git blame, so each commit must be fully self contained (which may necessarily mean larger commits for important refactoring).
September 1, 2025 at 3:16 PM
@ArneBab there is need to to break git blame, so each commit must be fully self contained (which may necessarily mean larger commits for important refactoring).
@ArneBab
atomic PR: addesses one issue, so that e.g. distro maintainer can cherry-pick commit to backport (I got often hard responses before we introduced this policy - for good reason if you look closely enough).
atomic PR: addesses one issue, so that e.g. distro maintainer can cherry-pick commit to backport (I got often hard responses before we introduced this policy - for good reason if you look closely enough).
August 28, 2025 at 8:23 AM
@ArneBab
atomic PR: addesses one issue, so that e.g. distro maintainer can cherry-pick commit to backport (I got often hard responses before we introduced this policy - for good reason if you look closely enough).
atomic PR: addesses one issue, so that e.g. distro maintainer can cherry-pick commit to backport (I got often hard responses before we introduced this policy - for good reason if you look closely enough).