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>"
| # ************************************** | |
| # ** Get MAC address of a remote host ** | |
| def arpreq_ip(ip): | |
| # type: (str) -> Optional[str] | |
| import arpreq | |
| return arpreq.arpreq('192.168.1.1') | |
| def scapy_ip(ip): | |
| # type: (str) -> str | |
| """Requires root permissions on POSIX platforms. |
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>"
After reading Why I'm Frequently Absent from Open Source by James Long and listening the corresponding The Changelog episode, I dwelt on the idea and believe that open source maintainers...
Along this line of thinking I've created a set of descriptions for different levels at which a project might be maintained. A maintainer can use these to announce to their users the current ability that they have to dedicate to a pr
| #!/usr/bin/env python3 | |
| # A text filter for BBEdit. If it encounters a JSON error, it writes an error message | |
| # to stderr (appears in a new BBEdit window) and leaves the original text unaltered. | |
| # c.f. http://crisp.tumblr.com/post/2574967567/json-pretty-print-formatting-in-bbedit | |
| # c.f. http://blog.scottlowe.org/2013/11/11/making-json-output-more-readable-with-bbedit/ | |
| import json | |
| import sys | |
| def main(): |