See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| func TestRouter(t *testing.T) { | |
| used := "" | |
| mw1 := func(next http.Handler) http.Handler { | |
| return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { | |
| used += "1" | |
| next.ServeHTTP(w, r) | |
| }) | |
| } |
I’m currently working (I’m just at the beginning, and I’m quite slow) on a personal project that will use Keepass files (kdb and kdbx).
I tried to find some documentation about .kdb and .kdbx format, but I didn’t find anything, even in the Keepass official website. I you want to know how these file formats are structured, you must read Keepass’s source code. So I wrote this article that explains how Keepass file format are structured, maybe it will help someone.
| # use at your own risk, might eat hamster and nose dragons | |
| git branch -m master master-bak | |
| git checkout --orphan master | |
| git reset --hard | |
| git commit --allow-empty -m 'init' | |
| git merge --ff --squash master-bak | |
| git commit --amend | |
| git push --force |
| #!/bin/bash | |
| set -ex | |
| # Set up required sysctl params, these persist across reboots. | |
| cat > /etc/sysctl.d/99-kubernetes-cri.conf <<EOF | |
| net.bridge.bridge-nf-call-iptables = 1 | |
| net.ipv4.ip_forward = 1 | |
| net.bridge.bridge-nf-call-ip6tables = 1 | |
| EOF |