Taehyun Hwang HwangTaehyun

Modern Arch linux installation guide

Buy Me a Coffee

Using inlined HTML

<a href="https://www.buymeacoffee.com/gbraad" target="_blank"><img src="https://www.buymeacoffee.com/assets/img/custom_images/orange_img.png" alt="Buy Me A Coffee" style="height: 41px !important;width: 174px !important;box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;-webkit-box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;" ></a>

Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:

<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

to recover files that were added to the index but whose changes were lost (e.g. git reset --hard)

git fsck --unreachable | grep commit | cut -d\  -f3 | xargs git show

git fsck --unreachable to get all the items that are unreachable
grep commit to filter out all entries except for commits (the index will show up as a commit)
cut -d\ -f3 to filter out all but the SHA1s
xargs git show to show all of the contents of the objects.

Once you've identified the SHA1 that contains the changes that were lost, check it out to get the working tree back into the state of the index at the time git reset --hard was run.

	#!/usr/bin/env bash

	function log () {
	printf "%s %s\n" "->" "$1"
	}

	log "Updating all asdf-plugin remotes..."

	asdf plugin update --all

	<!-- MIT License -->
	<html>
	<head>
	<script>
	function generateKey(alg, scope) {
	return new Promise(function(resolve) {
	var genkey = crypto.subtle.generateKey(alg, true, scope)
	genkey.then(function (pair) {
	resolve(pair)
	})