summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2007-11-05 22:56:45 -0500
committerJoey Hess <joey@kodama.kitenet.net>2007-11-05 22:56:45 -0500
commit3ad98fee63b48c850c51648bf91eee8b28b137cf (patch)
tree95ed9f3d2e0709f4970825c0e1a5a8e256e84a7a
parentb30d829cc736eadb51d24bb0b4d5404b1f2fa460 (diff)
updates
-rw-r--r--README10
1 files changed, 5 insertions, 5 deletions
diff --git a/README b/README
index 4900eeb..d106248 100644
--- a/README
+++ b/README
@@ -65,7 +65,7 @@ A quick walkthrough of using etckeeper.
cd /etc
etckeeper init
-This `etckeeper init` command initialises an /etc/.git/ repository. This
+The `etckeeper init` command initialises an /etc/.git/ repository. This
command is careful to never overwrite existing files or directories in
/etc. It will create a `.gitignore` if one doesn't already exist, sets up
git hooks if they don't already exist, and so on. It does *not* commit any
@@ -124,9 +124,9 @@ control, the sky's the limit..
## configuration
-Each etckeeper command uses `run-parts` to run the executable files in
-`/etc/etckeeper/$command.d/`. By default these directories contain a bunch of
-symlinks to the actual files; you can remove or reorder the symlinks, or
+etckeeper uses `run-parts` to run the executable files in
+`/etc/etckeeper/$command.d/`. By default these directories contain a bunch
+of symlinks to the actual files; you can remove or reorder the symlinks, or
add your own custom files. Each individual file is short, simple, and does
only one action.
@@ -159,7 +159,7 @@ Two blog posts provided inspiration for techniques used by etckeeper:
isisetup (http://www.isisetup.ch/) has some of the same aims as etckeeper,
however, unlike it, etckeeper does not aim to be a git porcelain with its
own set of commands for manipulating the /etc repository. Instead,
-etckeeper provides a couple of simple tools and hooks for setting up an /etc
+etckeeper provides a simple setup procedure and hooks for setting up an /etc
repsository, and then gets out of your way; you manage the repository using
regular git commands.