summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@frugalware.org>2008-01-04 18:32:25 +0100
committerJoey Hess <joey@kodama.kitenet.net>2008-01-04 12:59:47 -0500
commit769093aa22ab6102dc8f86fa6cb923618e3a5950 (patch)
tree23d3f1596e5c7d20e2dc5d8b5b2fba9d326b037c /README
parent649cc66c702fe34724ad9c34ea9a06efc7de7123 (diff)
replace git-foo with git foo
from the release notes of the upcoming 1.5.4 release: "The next feature release of git (this change is scheduled for v1.6.0) will by default install dashed form of commands (e.g. "git-commit") outside of users' normal $PATH"
Diffstat (limited to 'README')
-rw-r--r--README12
1 files changed, 6 insertions, 6 deletions
diff --git a/README b/README
index c4887c5..6dbffeb 100644
--- a/README
+++ b/README
@@ -66,7 +66,7 @@ A quick walkthrough of using etckeeper. 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 files into to git, but does `git-add` all
+and so on. It does *not* commit any files into to git, but does `git add` all
interesting files for an initial commit.
etckeeper init
@@ -106,7 +106,7 @@ make sure you run "etckeeper init" again, to get any metadata changes:
etckeeper init
Often it's better to clone /etc to elsewhere and do potentially dangerous
-stuff in a staging directory. You can clone the repository using git-clone,
+stuff in a staging directory. You can clone the repository using git clone,
but be careful that the directory it's cloned into starts out mode 700, to
prevent anyone else from seeing files like shadow, before `etckeeper init`
fixes their permissions:
@@ -120,7 +120,7 @@ fixes their permissions:
chmod 755 ..
Another common reason to clone the repository is to make a backup to a
-server. When using git-push to create a new remote clone, make sure the new
+server. When using git push to create a new remote clone, make sure the new
remote clone is mode 700! (And, obviously, only push over a secure
transport like ssh, and only to a server you trust.)
@@ -144,13 +144,13 @@ For example, here's how to configure it to run `git gc` after each apt run,
which will save a lot of disk space:
cd /etc/etckeeper/post-install.d
- (echo '#!/bin/sh' ; echo 'exec git-gc') > 99git-gc
+ (echo '#!/bin/sh' ; echo 'exec git gc') > 99git-gc
chmod +x 99git-gc
git add .
- git-commit -m "run git-gc after each apt run"
+ git commit -m "run git gc after each apt run"
Here's how to disable the automatic commits after each apt run, while still
-letting it git-add new files and git-rm removed ones:
+letting it git add new files and git rm removed ones:
chmod -x /etc/etckeeper/post-install.d/75git-commit