aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxero <x@xero.nu>2015-05-22 22:28:04 -0400
committerxero <x@xero.nu>2015-05-22 22:28:04 -0400
commit67a505f6ab918400bd311d2953afa805b622e51a (patch)
treea9d2c3276cccb454c2e1caec2c0d82467cbf76d7
parent453134c30f147e21e2d1e507782ef7dc2087b8ef (diff)
downloaddotfiles_ascii-67a505f6ab918400bd311d2953afa805b622e51a.tar.xz
dotfiles_ascii-67a505f6ab918400bd311d2953afa805b622e51a.zip
update README
-rw-r--r--README.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/README.md b/README.md
index 625ddc0..ca19e24 100644
--- a/README.md
+++ b/README.md
@@ -49,6 +49,7 @@ in the unix world programs are commonly configured in two different ways, via sh
it's been said of every console user:
> _"you are your dotfiles"_.
+
since they dictate how your system will look and function. to many users (see [ricers](http://unixporn.net) and [beaners](http://nixers.net)) these files are very important, and need to be backed up and shared. people who create custom themes have the added challenge of managing multiple versions of them. i have tried many organization techniques. and just take my word for it when i say, keeping a git repo in the root of your home directory is a bad idea. i've written custom shell scripts for moving or symlinking files into place. there are even a few dotfile managers, but they all seem to have lots of dependencies. i knew there had to be a simple tool to help me.
#managing