henrik

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

danielestevez

1) Create a branch with the tag
	git branch {tagname}-branch {tagname}
	git checkout {tagname}-branch

2) Include the fix manually if it's just a change .... 
	git add .
	git ci -m "Fix included"
    or cherry-pick the commit, whatever is easier
	git cherry-pick  {num_commit}
	

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

VladSumtsov

import java.util.List;

public interface DiskCache<T> {

    /**
     * Sets the value to {@code value}.
     */
    public void set(String key, T value);

    /**

AnderWeb

AppCompat-v7:21 provides a very useful way of dealing with pressed/focused/activated states maintaining backwards compatibility downto API-7, but there's a small issue (big for some) with the default selectableItemBackground: It uses some PNGs and/or default values for API<21.

The main reason is that android drawable resource definitions (prior API 21) CANNOT use theme attributes at all, so there's no way of making something like:
<shape android:shape="rectangle">
        <solid android:color="?attr/colorControlHighlight" />
</shape>

For this, I've put this simple mockup on how to give your app better drawables that the appcompat defaults.

Ozius

/*
mMap.addMarker(new MarkerOptions()
    .position(new LatLng(latitude, longitude))
    .title("Marker Title")
    .snippet("Marker snippet")
    .icon(getBitmapDescriptor(R.drawable.ic_place_black_48dp)));
*/

private BitmapDescriptor getBitmapDescriptor(int id) {
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {

fnk0

public interface BangAnimationListener {

    /**
     * <p>Notifies the start of the animation.</p>
     */
    void onAnimationStart();

    /**
     * <p>Notifies the end of the animation. </p>
     */

janojanahan

/**
 * A Gist proving that Kotlin's nullable type can be made into a monad without wrapping into another
 * object and satisfy the Monadic laws
 *
 * Kotlin has comprehensive null safety built into the language enforced at compile time, using its
 * nullable type.
 *
 * Its language structure makes dealing with nullable values simple and succinct. Unlike other language
 * monadic constructs such as Option (scala), Optional(Java8+) and Maybe(Haskell), it is enforced at
 * compile time and is compatible with existing non monad aware API (for example,

Brainiarc7

Tuning Intel Skylake and beyond for optimal performance and feature level support on Linux:

Note that on Skylake, Kabylake (and the now cancelled "Broxton") SKUs, functionality such as power saving, GPU scheduling and HDMI audio have been moved onto binary-only firmware, and as such, the GuC and the HuC blobs must be loaded at run-time to access this functionality.

Enabling GuC and HuC on Skylake and above requires a few extra parameters be passed to the kernel before boot.

Instructions provided for both Fedora and Ubuntu (including Debian):

Note that the firmware for these GPUs is often packaged by your distributor, and as such, you can confirm the firmware blob's availability by running: