Show more

It still needs a lot of work, but a proof of concept for window thumbnails in appears to work :) @purism

The next merge request will make cross the 1000 commit boundary:

```
$ git log --pretty=oneline | wc -l
999
```

@DelusionalAI Just for the reference for anyone who reads it and is interested:

1. git rebase -i COMMIT_ID^
2. choose "edit" in the commit you're interested in
3. git commit --amend --no-edit --author="Name Surname <email>"
4. git rebase --continue
5. git push --force-with-lease
6. ...
7. PROFIT

PS. It's "git", GitHub is irrelevant there ;)

@sir I think it's a confusion about what "git internals" really means. git plumbing != git's implementation details. git is a data structure manipulation tool, so you should know how that data structure looks like to use it effectively. It would be more like saying "you don't have to know how velocity works just to drive a car".

Multiple GTK apps open in the same environment and all fitting nice in the screen.
Thank you

After adding proximity sensor-support to -sensor-proxy (gitlab.freedesktop.org/hadess/) and adding runtime-pm support for the chip used in the (and it's devkit) (lore.kernel.org/linux-iio/cove) we can now wire it up to to fade the screen and prevent keyboard input:

A lot of people are confused by git. Most of these people, I reckon, learned it from the outside in - from the command-line interface down. If you started with git by asking "how do I sync up my changes with my peers", then you might get the answer, but you will be missing the foundation on which that answer is built. This is the main source of confusion with git.

The better way is to learn git from the inside out. You should first learn about what objects are and how they're stored and identified, and how they relate to each other. You should learn what blobs, trees, and commits actually are, and how they relate to each other, and how commits form a linked list from which a graph of all objects can be derived.

Then you should learn how the ref database gives friendly names like "master" and "feature/foobar" to objects, and how the reflog tracks changes to references over time.

THEN, and only then, should you learn how to use the CLI. Then you can learn about using the staging area to add objects to the database and create commits, and how doing this updates the reflog.

Git makes total sense when you approach it from this angle. Supposedly hard tools like git rebase are totally understandable when you view them with the appropriate foundational knowledge.

Git is a tool which you will reach for hundreds of times a day, every day, for your entire career. Maybe it's worth learning about properly.

Jonathan Carter on the "The apps are fast and responsive and just feel natural on this form factor. I’m looking forward again to having a pocket computer that can run Debian." - Random bits from FOSDEM 2020 jonathancarter.org/2020/02/07/

@joao @kaidan @kde@mastodon.technology Chatty, Dino, Kaidan... what to choose? ;D

Did you know that Plasma Mobile apps from KDE are working well on PureOS too? :) This is Kaidan, a Kirigami XMPP client, working smoothly on a Librem 5 @kaidan @kde@mastodon.technology

Finally tried the postmarketOS image with Plasma Mobile on my Librem 5 Birch! It's booting from an USB drive :D

freedesktop-sdk 19.08.07 has been released with Mesa 19.3 - which means that flatpaked apps can use OpenGL out-of-box with upstream unmodified runtime on the Librem 5 now! \o/
gitlab.com/freedesktop-sdk/fre

this laptop (MNT Reform) and this phone (Purism Librem 5) have the same SoC (CPU/GPU/...), i.MX8M. and both run free and open source drivers and software. #FOSDEM2020

Show more
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml