Deepika Upadhyay ideepika

A bunch of good git tutorials

Intro to git

Simplest intro to git by github and codeschool - Try Git
PeepCode Git Internals PDF
[Intro to github]

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

Git

Global Settings

Related Setup: https://gist.github.com/hofmannsven/6814278
Related Pro Tips: https://ochronus.com/git-tips-from-the-trenches/
Interactive Beginners Tutorial: http://try.github.io/
Git Cheatsheet by GitHub: https://services.github.com/on-demand/downloads/github-git-cheat-sheet/

Reminder

Press minus + shift + s and return to chop/fold long lines!

About programms

To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule

progrium/bashstyle

Bash is the JavaScript of systems programming. Although in some cases it's better to use a systems language like C or Go, Bash is an ideal systems language for smaller POSIX-oriented or command line tasks. Here's three quick reasons why:

It's everywhere. Like JavaScript for the web, Bash is already there ready for systems programming.
It's neutral. Unlike Ruby, Python, JavaScript, or PHP, Bash offends equally across all communities. ;)
It's made to be glue. Write complex parts in C or Go (or whatever!), and glue them together with Bash.

This document is how I write Bash and how I'd like collaborators to write Bash with me in my open source projects. It's based on a lot of experience and time collecting best practices. Most of them come from these two articles, but here integrated, slightly modified, and focusing on the most bang for buck items. Plus some ne

	# INSTALL INSTRUCTIONS: save as ~/.gdbinit
	#
	# DESCRIPTION: A user-friendly gdb configuration file.
	#
	# REVISION : 7.3 (16/04/2010)
	#
	# CONTRIBUTORS: mammon_, elaine, pusillus, mong, zhang le, l0kit,
	# truthix the cyberpunk, fG!, gln
	#
	# FEEDBACK: https://www.reverse-engineering.net

	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

	Lesson 1 SUMMARY


	1. The cursor is moved using either the arrow keys or the hjkl keys.
	h (left) j (down) k (up) l (right)

	2. To start Vim from the shell prompt type: vim FILENAME <ENTER>

	3. To exit Vim type: <ESC> :q! <ENTER> to trash all changes.
	OR type: <ESC> :wq <ENTER> to save the changes.

	#! /bin/bash
	set -e
	trap 'previous_command=$this_command; this_command=$BASH_COMMAND' DEBUG
	trap 'echo FAILED COMMAND: $previous_command' EXIT

	#-------------------------------------------------------------------------------------------
	# This script will download packages for, configure, build and install a GCC cross-compiler.
	# Customize the variables (INSTALL_PATH, TARGET, etc.) to your liking before running.
	# If you get an error and need to resume the script from some point in the middle,
	# just delete/comment the preceding lines before running it again.