docker rm $(docker ps -a -q)
docker rmi $(docker images -q)

Reference

link

git clone –bare https://github.com/%5BPUBLIC%5D.git –recursive
cd [PUBLIC].git/
git push –mirror https://github.com/%5BPRIVATE%5D.git
git remote -v
rm -rf [PUBLIC].git/
git clone https://github.com/%5BPRIVATE%5D.git –recursive
git remote -v
git remote add public https://github.com/%5BPUBLIC%5D.git

To fork as public…

https://help.github.com/articles/fork-a-repo/

https://stackoverflow.com/questions/22755268/clone-a-private-repo-of-github-with-username-and-password

1. rebase to one before whatever commits user hopes to change.
   – git rebase -i [HASH]
   
2. change pick to reword for commits user hopes to change.
3. quit vim using :wq
4. change message for each vim that pops up…
5. push to remote
   – git push –force

https://superuser.com/questions/751699/is-there-a-way-to-edit-a-commit-message-in-github/751909

docker rmi -f $(docker images -f “dangling=true” -q)

Reference

https://forums.docker.com/t/how-to-remove-none-images-after-building/7050/3

Create patch

git diff > patch.diff

Apply patch

patch -p1 < patch.diff

Reference

https://gist.github.com/zeuxisoo/980174

Usually, file are accessed using various functions. However, these seems to incur a lot of overhead. Therefore, for fast access, you would use mmap() to map certain variable to the memory address and lseek() would be used to move within that file.

There can be an example of this since usually this file is mapped to DRAM and it is volatile. To write this on the disk, you would use msync(). Failure can happen during the process, which is Failure-Atomic msync(). Terence Kelly seems to be actively working on this.

Reference

https://jameshfisher.com/2017/01/28/mmap-file-write.html

tail -f [My File]

Instruction

export PATH=$PATH:[My Path]