Mohammed Alshohayeb moshohayeb

e[dit]	evil-edit
w[rite]	evil-write
wa[ll]	evil-write-all
sav[eas]	evil-save
r[ead]	evil-read
b[uffer]	evil-buffer
bn[ext]	evil-next-buffer
bp[revious]	evil-prev-buffer
bN[ext]	bprevious
sb[uffer]	evil-split-buffer

`vs` Questions

http://stackoverflow.com/questions/804115 (rebase vs merge).
https://www.atlassian.com/git/tutorials/merging-vs-rebasing (rebase vs merge)
https://www.atlassian.com/git/tutorials/undoing-changes/ (reset vs checkout vs revert)
http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See git rev-parse)
http://stackoverflow.com/questions/292357 (pull vs fetch)
http://stackoverflow.com/questions/39651 (stash vs branch)
http://stackoverflow.com/questions/8358035 (reset vs checkout vs revert)

Core Coding Standard

Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.

	1. disable Base repo
	sed -i.bak '/^gpgcheck=1/ a enabled=0 ' /etc/yum.repos.d/CentOS-Base.repo

	2. append Vault repo with CentOS 6.7
	#-----------------

	[C6.7-base]
	name=CentOS-6.7 - Base
	baseurl=http://vault.centos.org/6.7/os/$basearch/
	gpgcheck=1

	# -- mode: ruby --
	# vi: set ft=ruby :

	Vagrant.configure(2) do \|config\|
	config.vm.box = "parallels/centos-7.3"

	#config.vm.network "forwarded_port", guest: 80, host: 8080
	config.vm.network "public_network"

	config.vm.provider "parallels" do \|v\|

Mohammed Alshohayeb moshohayeb

vs Questions

Core Coding Standard

Table Of Contents

Index

`vs` Questions