|
3 | 3 | .. |date| date::
|
4 | 4 |
|
5 | 5 | .. Version number is filled in automatically.
|
6 |
| -.. |version| replace:: 0.42-4 |
| 6 | +.. |version| replace:: 0.5 |
7 | 7 |
|
8 | 8 | git-notifier
|
9 | 9 | ============
|
@@ -89,8 +89,8 @@ mail will be send for that change.
|
89 | 89 | Download
|
90 | 90 | --------
|
91 | 91 |
|
92 |
| -The current release is `git-notifier 0.42 |
93 |
| -<http://www.icir.org/robin/git-notifier/git-notifier-0.42.tar.gz>`_ |
| 92 | +The current release is `git-notifier 0.5 |
| 93 | +<http://www.icir.org/robin/git-notifier/git-notifier-0.5.tar.gz>`_ |
94 | 94 |
|
95 | 95 | Not surprisingly, ``git-notifier`` is maintained in a git repository
|
96 | 96 | that you clone::
|
@@ -131,7 +131,6 @@ giving them on the command line, all of them can alse be set via
|
131 | 131 | address, do `` git config hooks.mailinglist [email protected]``:
|
132 | 132 |
|
133 | 133 | ``--allchanges <branches>``
|
134 |
| - |
135 | 134 | Lists branches for which *all* changes made to them should be
|
136 | 135 | mailed out as straight diffs to their previous state,
|
137 | 136 | independent of whether the corresponding commit has already
|
|
177 | 176 | path shown in the notification mails. Default is the
|
178 | 177 | canonical name of the system the script is running on.
|
179 | 178 |
|
| 179 | + ``--ignoreremotes`` |
| 180 | + If given, ``git-notifier`` will not report any commits that |
| 181 | + are already known by any configured remote repository. |
| 182 | + |
180 | 183 | ``--link <url>``
|
181 | 184 | Specifies a URL that will be included into notification mails
|
182 | 185 | for locating a changeset online. The URL can contain a "%s"
|
|
268 | 271 | Monitoring GitHub
|
269 | 272 | -----------------
|
270 | 273 |
|
271 |
| -.. note:: |
272 |
| - |
273 |
| - This is still experimental. |
274 |
| - |
275 | 274 | The ``git-notifier`` distribution comes with a companion script,
|
276 | 275 | ``github-notifier``, that watches GitHub repositories for changes. The
|
277 | 276 | script maintains a local mirror of repositories you want to watch and
|
@@ -300,13 +299,10 @@ subsequent executions, the script will update the clone and spawn
|
300 | 299 | ``git-notifier`` to email out notifications. For now, the best way to
|
301 | 300 | automate this is to run ``github-notifier`` from ``cron``.
|
302 | 301 |
|
303 |
| -.. note:: |
304 |
| - |
305 |
| - In the future we might add a daemon mode to ``github-notifier`` |
306 |
| - that keeps it running in the background, polling for updates |
307 |
| - regularly. Potentially it could even be triggered by a `GitHub web |
308 |
| - hook <https://help.github.com/articles/post-receive-hooks>`_ |
309 |
| - |
| 302 | +Note: In the future we might add a daemon mode to ``github-notifier`` |
| 303 | +that keeps it running in the background, polling for updates |
| 304 | +regularly. Potentially it could even be triggered by a `GitHub web |
| 305 | +hook <https://help.github.com/articles/post-receive-hooks>`_ |
310 | 306 |
|
311 | 307 | In the following we discuss more details of the configuration file.
|
312 | 308 |
|
|
0 commit comments