ocxo

#!/bin/bash

#####
# Builds a custom nginx
#
RELEASE_TAGS="nginx+custom"
RELEASE_MAINTAINER="Adam Ochonicki"
RELEASE_MAINTAINER_EMAIL="github.com@fromonesrc.com"
RELEASE_MESSAGE="Testing"

ocxo

require 'rubygems'
require 'right_aws'

aws_access_key_id = 'your-access-key'
aws_secret_access_key = 'your-secret-key'
target_bucket = 'your-source-bucket'
destination_bucket = 'your-destination-bucket'

s3 = RightAws::S3Interface.new(aws_access_key_id, aws_secret_access_key)

ocxo

OpenBSD -current works pretty well on my Mid-2011 Macbook Air (A1370, SandyBridge). The new KMS code brings up the MBA's eDP display in 1366x768 with backlight control. ACPI works as expected for battery/AC status, CPU throttling, and full suspend/resume support. The Broadcom wireless card does not work, so for now I am using this tiny USB adapter (urtwn) which is rather unobtrusive when plugged in.

Dual-booting with Mac OS X is fairly easy, but once FileVault is enabled for full-disk encryption of Mac OS, it clobbers the path to boot back into OpenBSD. Here's how to get both OSes working, each with its own disk encryption, without having to use rEFIt or anything else.

###Mac OS X Configuration

1. If FileVault is already enabled, turn it off and decrypt the SSD.

2. Use Boot Camp Assistant to partition the hard drive, slicing off a portion of the end of the drive for OpenBSD (I used 30Gb on a 256Gb SSD). If BCA jus

ocxo

#!/bin/sh
# Just copy and paste the lines below (all at once, it won't work line by line!)
# MAKE SURE YOU ARE HAPPY WITH WHAT IT DOES FIRST! THERE IS NO WARRANTY!

function abort {
  echo "$1"
  exit 1
}

set -e

ocxo

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 = git@github.com: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:

ocxo

Inspired by Mitchell Hashimoto's tweet:

I wish I could add a note to my branch on GitHub so people who viewed the branch could know why it exists. (Yeah, the README is one option)

I'd like to propose a unified BRANCH(.md) file.

Github already treats Contributing Guidelines as a special case, so why not add a BRANCH.md file.

This file would contain branch-specific information like: