diff options
| author | Joey Hess <joey@kodama.kitenet.net> | 2008-06-12 13:55:15 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kodama.kitenet.net> | 2008-06-12 13:55:15 -0400 |
| commit | 1f7f51828dfe1fe563d26d526fea563b4bb56b0d (patch) | |
| tree | 02e9e7cb1c9196c38f41aad993aa19430ac44d9a /doc/plugins/pingee | |
| parent | 465b1edc709870834595c83e31c5ac4c1fdad412 (diff) | |
| download | ikiwiki-1f7f51828dfe1fe563d26d526fea563b4bb56b0d.tar ikiwiki-1f7f51828dfe1fe563d26d526fea563b4bb56b0d.tar.gz | |
response
Diffstat (limited to 'doc/plugins/pingee')
| -rw-r--r-- | doc/plugins/pingee/discussion.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/plugins/pingee/discussion.mdwn b/doc/plugins/pingee/discussion.mdwn index 6a36093b8..a54caf235 100644 --- a/doc/plugins/pingee/discussion.mdwn +++ b/doc/plugins/pingee/discussion.mdwn @@ -1,3 +1,9 @@ I see that this code performs an RCS update to collect updates. Is there anything in this that would help propagate modifications to the other machine... or would this require a reciprocal pingee setup on the other end? -- [[harningt]] + +> The pingee won't push any pending updates it has back to the pinger, no. +> But often the pinger is the origin of the rcs checkout on the pingee, and +> if so, ikiwiki defaults to automatically pushing updates to the origin +> when they are made. Or you can set up a reciprocal pingee/pinger setup as +> described. --[[Joey]] |