projects
/
ikiwiki.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
d9e3470
)
spelling, grammar
author
https://launchpad.net/~kralph
<kralph@web>
Wed, 26 Jan 2011 15:57:44 +0000
(15:57 +0000)
committer
Joey Hess
<joey@kitenet.net>
Wed, 26 Jan 2011 15:57:44 +0000
(15:57 +0000)
doc/rcs/git.mdwn
patch
|
blob
|
history
diff --git
a/doc/rcs/git.mdwn
b/doc/rcs/git.mdwn
index c627792d7bb858e67885b1fc3fac087efd09ca00..1b66493dddad9fe24a798909bd3931aa801c5e51 100644
(file)
--- a/
doc/rcs/git.mdwn
+++ b/
doc/rcs/git.mdwn
@@
-56,8
+56,8
@@
repositories:
repositories are also clones of the bare root repository above --
and these have a working directory for you to work on. Use either
the `git` transport (if available), or `ssh`. These repositories may
repositories are also clones of the bare root repository above --
and these have a working directory for you to work on. Use either
the `git` transport (if available), or `ssh`. These repositories may
- be on remote machines, your laptop, where
e
ver you find convenient to
- hack on your wiki.
y
ou can commit local changes to the version on
+ be on remote machines, your laptop, wherever you find convenient to
+ hack on your wiki.
Y
ou can commit local changes to the version on
the laptop, perhaps while offline. Any new content should be pushed to the
bare master repository when you are ready to publish it, and then
the post-update hook of the bare repository will ensure that the
the laptop, perhaps while offline. Any new content should be pushed to the
bare master repository when you are ready to publish it, and then
the post-update hook of the bare repository will ensure that the