Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
Gerrit version 2.8 | |
Replication plugin extracted from gerrit.war and installed over ssh | |
Installation method -> | |
a) Relevant configs: | |
/var/lib/gerrit/etc/replication.config | |
[remote "aricg-compliance"] | |
url = git@github.com:somerepo/${name}.git |
The documentation for Gerrit when it comes to formatting comments is quite lacking. Here is short list created by trial and error and looking at the source code in: | |
./gerrit-gwtexpui/src/main/java/com/google/gwtexpui/safehtml/client/SafeHtml.java | |
Lists: | |
* List item 1 | |
* List item 2 | |
- List item 1 | |
- List item 2 |
/* | |
Example usage (in configuration.nix): | |
services.phabricator.enable = true; | |
services.phabricator.baseURI = "secure.example.org"; | |
services.phabricator.baseFilesURI = "secure-files.example.org"; | |
services.phabricator.extensions = | |
{ libphutil-scrypt = "git://github.com/haskell-infra/libphutil-scrypt.git"; | |
libphutil-yubikey = "git://github.com/thoughtpolice/libphutil-yubikey.git"; |
package main | |
import ( | |
"flag" | |
"fmt" | |
"log" | |
"net/http" | |
"os" | |
"golang.org/x/net/webdav" |
package main | |
import ( | |
"crypto/tls" | |
"crypto/x509" | |
"flag" | |
"fmt" | |
"io/ioutil" | |
"log" | |
"os" |
This is a slightly stripped down version from our internal bug tracker. The point of posting this publicly is part FYI, part peer review. I'm hoping someone can look at this, disagree, and tell me all the downsides of using the C
locale or point out things I've misunderstood. The Recommendations
section in particular is contextualized by our database serving a SaaS product for users from many different locales, thus making locale a render level concern. YMMV, caveat emptor, etc.
Collation defines the character ordering for textual data. For Postgres, https://www.postgresql.org/docs/current/static/locale.html:
The locale settings influence the following SQL features:
- Sort order in queries using ORDER BY or the standard comparison operators on textual data
- The
upper
,lower
, andinitcap
functions
#!/bin/sh | |
# | |
# git-push-to-target: Force push with lease this commit to a branch specified in its | |
# commit description like `branch: jake/my-branch`: | |
# | |
# `git-push-to-target --query` will do a dry run and print the branch name it detects | |
# `git-push-to-target --pick` will pick this to it's own branch off master and push. | |
# | |
# Usage within an interative rebase, add this after each commit that contains the branch directive: | |
# > exec git push-to-target |