SWW13

Das war möglicherweise etwas unpräzise ausgedrückt von mir, aber genau was ich sagen wollte.

Unter dem Ausdruck Arbeitskleidung kann man viel verstehen, was nicht alles abdeckt sein muss. Solange das nicht bereits der Betriebsrat geklärt hat, müsste man das im Zweifel auch erst vor Gericht klären. Wenn also den Status quo bisher noch keiner angefochten hat - alle Kollegen ziehen sich in der Freizeit um - dann ist das im Zweifel nicht das stärkste Argument im Disput mit der Leitung.

Sicher sind absolute Aussagen auf Basis schwammiger Informationen deutlich hilfreicher, als ein kleiner Hinweis das es sich möglicherweise um eine Grauzone handeln könnte.

Ich kenn zwar deine genauen Umstände nicht, so weit ich weiß gilt der Regel mit der Umziehzeit nur für spezielle Arbeitskleidung, also sowas wie Sicherheitsshuhe oder Helm, was man außerhalb der Arbeit nicht tragen darf / möchte. Also je nach dem was für Arbeitskleidung du hast und was euer Betriebsrat dazu sagt gilt die Regel eventuell erstmal nicht oder nur für einen Teil der Kleidung. Ansprechen schadet sicher nicht, es ist nur nicht so offensichtlich wie das nutzen der Pause zum Schlafen.

Ouch, hope you can get that sorted out. A broken disk my also "deadlock" the system when binaries it tries to start are on that disk and no longer in cache, e.g. sshd or your shell.

In my experience when only ping sporadically works it's an OOM issue, if the ssh login fails weirdly it can also be an I/O issue. If your network is working as expected obviously.

Look into earlyoom or systemd-oomd, the kernel out-of-memory killer will only start killing processes way after it should be. It will happily deadlock itself in a memory swap loop before considering killing any process.

There are a lot of other ways to fine tune the kernel to prevent this, but it's a good starting point to prevent your system from freezing. Just keep in mind it will kill processes when memory is running out until enough memory is available.

You can use a git client to connect to SVN repo, which is really neat if you have to deal with a SVN repo. Therefore I would assume git has no issues with migrating the history from SVN.

Es scheint sich nur um die Auslandsverbindungen während der EM zu handeln:

Diese ist jedoch auf die Sommermonate Juni, Juli und August beschränkt. Betroffen sind fast alle internationale Fernverbindungen mit dem ICE, IC oder EC.

As some who has played maybe 30-50% of DOS1+2 and currently the first of three acts in BG3: If you have issues with the gameplay mechanics in DOS1/2 you'll likely have them in BG3 too. Main difference is a vastly improved storyline, which kinda makes up for most of them.

Issues I still have with BG3 boils down to only the active character can use its abilities in conversations and sometimes (mechanically) unexpected stuff happens that can only be undone by saves.

If your issue with DOS was a boring story and lack of hidden/funny things to uncover you should give BG3 a try, if you disliked the overall experience you likely won't enjoy BG3.

I got myself a vertical mouse and no longer grind down my wrist on the table. Definitely worth every penny.

I used to have the Microsoft Explorer mouse which is a bit larger, I used it for over 5 years per mouse. The old version is no longer available and the new one looked terrible, that got me into looking for alternatives in the first place.

But if you're okay with the default mouse sizes and don't have other issues they are fine too.

If you are looking for something specific or a category of crate you may want to checkout lib.rs, a great alternative frontend for crates.

Good point, this could just misrepresentat the situation. I also haven't looked over the mailing list thread and comments here are very salty.

But giving him the benefit of doubt of a nice potential contributer who just debugged a very hard issue and sending in a basic concept of a potential fix. I think it would be beneficial for their community to take the wish for more credit more serious and try to make him feel welcome. But I recognize it was probably hard to do in this case.

Overall I just wanted to recognize that I do see how he feels robbed of his contribution. It reminded me that I also had an experience with the kernel developers that made me not want to contribute again.

I didn't meant to defend the patch and I see your point. But I personally think that it's not unreasonable to expect to land a bugfix commit after spending multiple days debugging a complex issue, that's why understand that he feels robbed of a kernel contribution.

I don't know what could have been a good solution for this scenario. But taking potential future contributors feelings more serious would help to keep them around and make them feel appreciated.

That's what I meant, using your shell to run command line tools to solve your issue at hand. And having a powerful shell with e.g. context dependend autocomplete (and a lot more) helps to speed up that task.