ejholmes

git merge-base --is-ancestor master HEAD

from man git merge-base

A common idiom to check "fast-forward-ness" between two commits A and B is (or at least used to be) to compute the merge base between A and B, and check if it is the same as A, in which case, A is an ancestor of B. You will see this idiom used

ejholmes

input {
    tcp {
        port => 1514
        type => "syslog"
        tags => ["input_heroku_syslog"]
    }
}
 
output {
  stdout { 

ejholmes

#!/bin/bash

# Setup and start Sauce Connect for your TravisCI build
# This script requires your .travis.yml to include the following two private env variables:
# SAUCE_USERNAME
# SAUCE_ACCESS_KEY
# Follow the steps at https://saucelabs.com/opensource/travis to set that up.
#
# Curl and run this script as part of your .travis.yml before_script section:
# before_script:

ejholmes

extern mod std;

fn is_three(num: int) -> bool {
  num % 3 == 0
}

#[test]
fn test_is_three() {
  assert is_three(1) == false;
  assert is_three(3) == true;

ejholmes

<script type="text/javascript">
    $(function() {
        Player.setup({
            jwplayer: 'demoplayer/jwplayer',
            playlist: [
                {
                    duration: 320,
                    image: 'images/tid-poster.png',
                    title: 'Tidemark',
                    levels: [ { file: 'video/tid-videostring-v02.mp4' } ]

ejholmes

Beta Features

• Log Convetnions
• Last Value Computation

To use the beta log conventions, prepend the drain url path with /beta.

For instance:

ejholmes

source "http://rubygems.org"
gem "janky", "~>0.9"
gem "pg"
gem "thin"