37 karma · joined February 26, 2017
* Use
* bullet
* points
* aggressively
Fixed that for you> Use the imperative mood in the subject line
The only rationales I've seen for using imperative ("fix bug") over the indicative ("fixed bug") are that it's what git does by default anyways.
Is it really that big of a deal to use the indicative sometimes and imperative other times?
For what it's worth, I always write commit messages in the imperative, out of habit. When others write commit messages in the indicative tense, part of me notices, but I move on because I can still understand the message if it adheres to the other guidelines.
Some background: https://github.com/2factorauth/twofactorauth/issues/5238
> The Sun's luminosity has risen by 10%, causing Earth's surface temperatures to reach an average of c. 320 K (47 °C; 116 °F). The atmosphere will become a "moist greenhouse", resulting in a runaway evaporation of the oceans.[65][70] This would cause plate tectonics to stop completely, if not already stopped before this time.[71]
Would somebody be able to ELI5 the connection the Earth's average temperature and plate tectonics?
feels more like r/AskReddit to me
For example, if you want to transfer your stuff from Evernote into StandardNotes, you can export your note content as ENEX and use a conversion tool for it. https://dashboard.standardnotes.org/tools
Unfortunately neither export file nor the provided import tool handle Notebook info (StandardNotes doesn't have notebooks but it can approximated with tags).
So this tool creates some of that missing metadata that is extracted from the export service and is converted into a format that can understood by the import service.
My favorite part is "THE OFFICIAL U.S. TIME".
No messing around.
search for "Figure 7"