li2

package net.stf.threelevelexpandablelistview;

import android.content.Context;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.BaseExpandableListAdapter;
import android.widget.ExpandableListView;

li2

/** 
 * usbreset -- send a USB port reset to a USB device
 * Compile using: gcc -o usbreset usbreset.c
 */
#include <stdio.h>
#include <unistd.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/ioctl.h>

li2

module Jekyll

  Page.class_eval {
  
    def clone
      Page.new(@site, @base, @dir, @name)
    end

  }

li2

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

li2

li2

For this I'd use:

gitk [filename]

or to follow filename past renames

gitk --follow [filename]

li2

The core idea behind the Feature Branch Workflow is that all feature development should take place in a dedicated branch instead of the master branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. It also means the master branch will never contain broken code, which is a huge advantage for continuous integration environments.

pull requests make it incredibly easy for your team to comment on each other’s work.

link: Git Feature Branch Workflow

Start with the master branch

git checkout master

li2

If referential integrity has been broken:

git config --get remote.origin.url

If referential integrity is intact:

git remote show origin

li2

//

li2

Default

Powerlevel9k