This is an OpenPGP proof that connects my OpenPGP key to this Github account. For details check out https://docs.keyoxide.org/advanced/openpgp-proofs/
[Verifying my OpenPGP key: openpgp4fpr:F39CD46349A576F88EF924791102102EBE7C3AE4]
This is an OpenPGP proof that connects my OpenPGP key to this Github account. For details check out https://docs.keyoxide.org/advanced/openpgp-proofs/
[Verifying my OpenPGP key: openpgp4fpr:F39CD46349A576F88EF924791102102EBE7C3AE4]
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
#!/bin/bash | |
# btrfs-undelete | |
# Copyright (C) 2013 Jörg Walter <info@syntax-k.de> | |
# This program is free software; you can redistribute it and/or modify it under | |
# the term of the GNU General Public License as published by the Free Software | |
# Foundation; either version 2 of the License, or any later version. | |
if [ ! -b "$1" -o -z "$2" -o -z "$3" ]; then | |
echo "Usage: $0 <dev> <file/dir> <dest>" 1>&2 | |
echo |