| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
- stop depending on Perl in slugify();
- stop relying on GNU sed extensions on slugify();
- use optional flags over positional arguments;
- use POSIX "date +%Y-%m-%d" over "date -I";
- always read from STDIN instead of deciding based on the input;
- don't rely on GNU coreutils' `mktemp`;
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
From RFC 5322 [0]:
> When used in a reply, the field body MAY start with the
> string "Re: " (an abbreviation of the Latin "in re", meaning "in the
> matter of") followed by the contents of the "Subject:" field body of
> the original message.
[0]: https://www.rfc-editor.org/rfc/rfc5322
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
-failure-scenarios.md: Use correct update dates
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
note on obsolete Git Protocol server
|
| | |
|
| | |
|
| |
|
|
| |
favicon that has white background
|
| | |
|
| | |
|
| | |
|
