THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
proxy_cache_path /repo_cache use_temp_path=off keys_zone=repo_cache:5m max_size=20g inactive=7d; | |
server { | |
server_name _; | |
listen 80; | |
proxy_cache repo_cache; | |
# if the backend is not reachable use cache | |
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504; |
Personally, I was never ambitious enough to spur my own descendants. | |
Yet this world and all the descendants of millions of people need to be thought about. | |
They deserve it to be left with a planet and people who are above my generation's average capacity. | |
My couple of suggestions to everyone who is involved with or has influence on the coming development: | |
1) Refrain from jealousy. Granting everything to anyone is a good start. | |
2) Don't waste your time with malicious gossip. It'll return to you rather sooner than later. | |
3) If you like someone, tell them. The day when it will be too late to speak out is coming soon. | |
4) Kindliness brings you US$ 0.00 per barrel. Sell it! |
alias co='git checkout' | |
alias ci='git commit' | |
alias ga='git add' | |
alias addp='git add -p' | |
alias status='git status' | |
alias gdiff='git diff' | |
alias gpatch='git diff --no-prefix' | |
alias show='git show' | |
alias wdiff='git wdiff' | |
alias br='git branch' |
This work is released under a Creative Commons Attribution-NoDerivatives 4.0 International License.
"OpenPGP" refers to the OpenPGP protocol, in much the same way that HTML refers to the protocol that specifies how to write a web page. "GnuPG", "SequoiaPGP", "OpenPGP.js", and others are implementations of the OpenPGP protocol in the same way that Mozilla Firefox, Google Chromium, and Microsoft Edge refer to software packages that process HTML data.
see https://github.com/rlcamp/coroutine |
# usage: | |
# cd $XBPS_DISTDIR | |
# ./deps.sh | |
# ./loops.py builddeps $XBPS_DISTDIR/srcpkgs | |
mkdir -p builddeps | |
find srcpkgs -mindepth 1 -maxdepth 1 | cut -d/ -f2 | while read pkg; do echo ' '$pkg; ./xbps-src show-build-deps $pkg > builddeps/$pkg; done |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to