Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| > cat .zshfunc/vnc | |
| # -*- sh -*- | |
| ## vim:ft=zsh:foldmethod=marker | |
| local HOST VM | |
| if [ $# -lt 2 ]; then | |
| echo "Usage: $0 HOST VM" | |
| return | |
| fi |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
| <?php | |
| /** | |
| * Set global/skip_process_modules_updates to '1' in app/etc/local.xml and | |
| * then use this script to apply updates and refresh the config cache without | |
| * causing a stampede on the config cache. | |
| * | |
| * @author Colin Mollenhour | |
| */ | |
| umask(0); | |
| ini_set('memory_limit','512M'); |
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2108403/hack.sh | sh | |
| # |
| check out pry screencast here http://pry.github.com/screencasts.html | |
| install pry | |
| $ gem install pry pry-doc | |
| start shef | |
| $ shef | |
| # load pry | |
| chef> require 'pry' |
Adrian -
I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.
You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,
MITRE has this thing called "CEE" - Common Event Expression.
CEE is a failure because, while claiming to be a standards effort, it maximizes incompatibility between implementations by doing the following:
| ruby_block "configure #{p} module" do | |
| block do | |
| require 'chef/util/file_edit' | |
| nc = Chef::Util::FileEdit.new("/etc/reconnoiter/noit.conf") | |
| nc.insert_line_after_match(/lua.*noit.module.smtp/, "<module loader=\"lua\" name=\"#{p}\" object=\"noit.module.#{p}\"/>") | |
| nc.write_file | |
| Chef::Log.info "Inserted module config for #{p}" | |
| end |
| <!-- the env variables are controlled by Chef and passed in via -D on the java command-line --> | |
| <!-- This is using the appender here: https://github.com/t0xa/gelfj --> | |
| <appender name="graylog2" class="org.graylog2.log.GelfAppender"> | |
| <param name="graylogHost" value="${graylog.server}"/> | |
| <param name="originHost" value="${graylog.origin}"/> | |
| <param name="extractStacktrace" value="true"/> | |
| <param name="addExtendedInformation" value="true"/> | |
| <!-- The _web part is because a given app has multiple components --> | |
| <!-- This app might have a _web as well as an _batch component --> | |
| <param name="facility" value="${graylog.facility}_web"/> |
