Skip to content

Instantly share code, notes, and snippets.

2019-11-12 20:13:54 Starting parachain attestation session on top of parent 0x31b789dee87486242c86d246b4a954227a943b50b6defe9c8
21eab73d688f718. Local parachain duty is Some(LocalDuty { validation: Relay })\n
06Z"}
2019-11-12 20:13:56 Idle (40 peers), best: #641134 (0x31b7…f718), finalized #641132 (0x8609…9128), ⬇ 207.8kiB/s ⬆ 247.9kiB/s\n"
,"stream":"stderr","time":"2019-11-12T20:13:56.786940054Z"}
Hash: given=5afd7888e359e829b7fd3174a79a7ab892955088a143df83715e0eab95d87a8f, expected=08a79fec94ba98c668aeabd73f18707897bc1f3b
ba40e66bd386e709e9e20d31\n
\n
====================\n
\n
@plumex
plumex / tmux-cheatsheet.markdown
Created July 18, 2016 08:16 — forked from MohamedAlaa/tmux-cheatsheet.markdown
tmux shortcuts & cheatsheet

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname
@plumex
plumex / git.migrate
Created April 18, 2016 06:15 — forked from niksumeiko/git.migrate
Moving git repository and all its branches, tags to a new remote repository keeping commits history
#!/bin/bash
# Sometimes you need to move your existing git repository
# to a new remote repository (/new remote origin).
# Here are a simple and quick steps that does exactly this.
#
# Let's assume we call "old repo" the repository you wish
# to move, and "new repo" the one you wish to move to.
#
### Step 1. Make sure you have a local copy of all "old repo"
### branches and tags.