| A good commit message looks like this: | |
| Header line: explaining the commit in one line | |
| Body of commit message is a few lines of text, explaining things | |
| in more detail, possibly giving some background about the issue | |
| being fixed, etc etc. | |
| The body of the commit message can be several paragraphs, and | |
| please do proper word-wrap and keep columns shorter than about |
Working with protobuf in Go puts significant load on the memory subsystem, as protobuf-generated structures often contain a significant amount of pointers.
One way to minimize the number of allocations is to allocate all the fields at the same time, and then use internal pointers to wire them up.
Let's pretend you have (the generated Go code for) four messages A, B, C, and D (note: for clarity this is not really protobuf-generated code, but the technique
| #!/bin/bash | |
| # Location of your restic repo | |
| export RESTIC_REPOSITORY=/run/media/kenneth/MyBook/restic | |
| # Password of the restic repo | |
| # Use a keyring to store the password so it isn't stored in plaintext on disk | |
| # Install python-keyring (Arch) to use this command | |
| export RESTIC_PASSWORD=`keyring get restic MyBook` | |
| if ! restic snapshots |