@ 260802.2

210511.1 · e83a20184ede07917dc95aee645af83cef52c824

doc: move to .github directory

Looks like this will cause the README to show up on the main page. Kudos to RecklessGeek on reddit.[1]

[1] - https://old.reddit.com/r/rust/comments/n9ssl6/what_do_you_use_for_writing_rust_code/gxsp01o/?context=3

reading declarations

.doc/README.md

deleted file mode 100644@@ -1,53 +0,0 @@-My dotfiles-------------This repository contains a my home directory setup, including a large-collection of personal scripts. I've built up this configuration over many-years, but had never intended on making it public. Because of a few-idiosyncracies in my previous setup, and after getting requests to share my-dotfiles, I decided to scrub everything clean and start fresh.--Licensed under the [UNLICENSE](https://unlicense.org).---How it's used---------------Other than git and a few helper scripts, there's no tool I used to "manage" my-dotfiles. Namely, my home directory *is* a git clone. That is, `$HOME/.git`-exists. So to set up my dotfiles on a new machine, I usually do something like-this:--```-mkdir -p tmp/old-mv .bashrc .bash_profile other things tmp/old-git init-git remote add origin https://github.com/BurntSushi/dotfiles-git pull origin master --ff-only-git branch --set-upstream-to origin/master master-chmod 0600 "$HOME/.ssh/config"-```--Then I log out and log back in. Most of this process is automated in my-`bin/setup-home` script. I host the latest version of that script at-https://burntsushi.net/stuff/setup-home for convenience.--In order to manage device specific configuration (e.g., my laptop and my-desktop use a different font size for my terminal configuration), I use a-simple symlinking scheme based on hostname. To create symlinks, run-`setup-home-links`.--Note that some files in this repository, such as my SSH configuration, are-encrypted.---Motivation------------In general, I'm making this public for the purposes of edification and easy-sharing. It is not a goal for this setup to be used and supported by others.-With that said, small fixes to existing scripts or suggestions on how to-improve my setup are welcome.---Caveats---------I may occasionally rewrite history of this repository and force push. This may-occur if I discover that I have accidentally published sensitive information.

.doc/UNLICENSE

deleted file mode 100644@@ -1,24 +0,0 @@-This is free and unencumbered software released into the public domain.--Anyone is free to copy, modify, publish, use, compile, sell, or-distribute this software, either in source code form or as a compiled-binary, for any purpose, commercial or non-commercial, and by any-means.--In jurisdictions that recognize copyright laws, the author or authors-of this software dedicate any and all copyright interest in the-software to the public domain. We make this dedication for the benefit-of the public at large and to the detriment of our heirs and-successors. We intend this dedication to be an overt act of-relinquishment in perpetuity of all present and future rights to this-software under copyright law.--THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.-IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR-OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,-ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR-OTHER DEALINGS IN THE SOFTWARE.--For more information, please refer to <http://unlicense.org/>

.github/README.md

new file mode 100644@@ -0,0 +1,53 @@+My dotfiles+-----------+This repository contains a my home directory setup, including a large+collection of personal scripts. I've built up this configuration over many+years, but had never intended on making it public. Because of a few+idiosyncracies in my previous setup, and after getting requests to share my+dotfiles, I decided to scrub everything clean and start fresh.++Licensed under the [UNLICENSE](https://unlicense.org).+++How it's used+-------------+Other than git and a few helper scripts, there's no tool I used to "manage" my+dotfiles. Namely, my home directory *is* a git clone. That is, `$HOME/.git`+exists. So to set up my dotfiles on a new machine, I usually do something like+this:++```+mkdir -p tmp/old+mv .bashrc .bash_profile other things tmp/old+git init+git remote add origin https://github.com/BurntSushi/dotfiles+git pull origin master --ff-only+git branch --set-upstream-to origin/master master+chmod 0600 "$HOME/.ssh/config"+```++Then I log out and log back in. Most of this process is automated in my+`bin/setup-home` script. I host the latest version of that script at+https://burntsushi.net/stuff/setup-home for convenience.++In order to manage device specific configuration (e.g., my laptop and my+desktop use a different font size for my terminal configuration), I use a+simple symlinking scheme based on hostname. To create symlinks, run+`setup-home-links`.++Note that some files in this repository, such as my SSH configuration, are+encrypted.+++Motivation+----------+In general, I'm making this public for the purposes of edification and easy+sharing. It is not a goal for this setup to be used and supported by others.+With that said, small fixes to existing scripts or suggestions on how to+improve my setup are welcome.+++Caveats+-------+I may occasionally rewrite history of this repository and force push. This may+occur if I discover that I have accidentally published sensitive information.

.github/UNLICENSE

new file mode 100644@@ -0,0 +1,24 @@+This is free and unencumbered software released into the public domain.++Anyone is free to copy, modify, publish, use, compile, sell, or+distribute this software, either in source code form or as a compiled+binary, for any purpose, commercial or non-commercial, and by any+means.++In jurisdictions that recognize copyright laws, the author or authors+of this software dedicate any and all copyright interest in the+software to the public domain. We make this dedication for the benefit+of the public at large and to the detriment of our heirs and+successors. We intend this dedication to be an overt act of+relinquishment in perpetuity of all present and future rights to this+software under copyright law.++THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.+IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR+OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR+OTHER DEALINGS IN THE SOFTWARE.++For more information, please refer to <http://unlicense.org/>