For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
" Don't try to be vi compatible | |
set nocompatible | |
" Helps force plugins to load correctly when it is turned back on below | |
filetype off | |
" TODO: Load plugins here (pathogen or vundle) | |
" Turn on syntax highlighting | |
syntax on |
This document attempts to refine Python's PEP 440 to include the principles of Semantic Versioning.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
If your vim distribution uses vim-plug
and includes plugins you don't want, or if you want to simply maintain a single set of plugins but disable some on certain machines, this may be for you.
let g:plugs_disabled = []
function! plug_disable#commit()
for name in g:plugs_disabled
#!/usr/bin/env bash | |
set -Eeuo pipefail | |
trap cleanup SIGINT SIGTERM ERR EXIT | |
script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P) | |
usage() { | |
cat <<EOF | |
Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...] |
As far as I can tell, you can't do it conveniently. That is, git-rebase
does not give you an option to preserve the committer date. Unless you give the --ignore-date
(or its alias, --reset-author-date
) option, it will always preserve the author date. However, there is no way to make git-rebase
preserve the committer date, unless some manual script is crafted.
The best you can do is to make the committer date equal to the author date. Recently (in 2020 Q4), git-rebase --interactive
has gained the ability to use the --committer-date-is-author-date
flag with the interactive rebase. Before that, there was no way of influencing the committer date at all with the interactive rebase. Note that this flag does not preserve the committer date. It merely makes the committer date equal to the author date.
You might be thinking "well, isn't that effectively preserving the committer date, since normally the committer date is always equal to the author date?". Normally, you would be correct. However, there