Mercurial > hg-allpaths
comparison README.txt @ 41:b8a7342fbf23
outgoingall and incomingall can't handle -g as it is already taken,
sticking to just --group
author | Marcin Kasperski <Marcin.Kasperski@mekk.waw.pl> |
---|---|
date | Sat, 24 Sep 2016 23:06:23 +0200 |
parents | c27e23a3509c |
children | e710d5bec0b5 |
comparison
equal
deleted
inserted
replaced
40:1c22cd2904eb | 41:b8a7342fbf23 |
---|---|
49 Instead of pushing/pulling everywhere, you can define and use *groups*:: | 49 Instead of pushing/pulling everywhere, you can define and use *groups*:: |
50 | 50 |
51 hg pushall -g publish | 51 hg pushall -g publish |
52 | 52 |
53 pushes to all paths from the ``publish`` group (where ``publish`` is | 53 pushes to all paths from the ``publish`` group (where ``publish`` is |
54 symbolic name of your choosing). | 54 symbolic name of your choosing). Or:: |
55 | |
56 hg pullall -g shared | |
57 | |
58 pulls from all paths in ``shared`` group. | |
55 | 59 |
56 There are two ways to define such a group: | 60 There are two ways to define such a group: |
57 | 61 |
58 1. Define appropriate entry in ``[all_paths]`` section (either in ``.hg/hgrc`` | 62 1. Define appropriate entry in ``[all_paths]`` section (either in ``.hg/hgrc`` |
59 or in your global ``~/.hgrc``). For example:: | 63 or in your global ``~/.hgrc``). For example:: |
84 | 88 |
85 I recommend the former method as it avoids the risk of conflicts, | 89 I recommend the former method as it avoids the risk of conflicts, |
86 makes it easy to define groups globally instead of defining them for | 90 makes it easy to define groups globally instead of defining them for |
87 every repository (especially handy if you use `Path Pattern`_), and is | 91 every repository (especially handy if you use `Path Pattern`_), and is |
88 more compact. | 92 more compact. |
93 | |
94 Groups are also handled for ``incomingall`` and ``outgoingall``, but | |
95 long ``--group`` option must be used (``-g`` is already taken by | |
96 standard Mercurial, means reporting in ``--git`` diff format):: | |
97 | |
98 hg outgoingall --group publish | |
89 | 99 |
90 Configuration | 100 Configuration |
91 ======================================================= | 101 ======================================================= |
92 | 102 |
93 The extension can be configured using ``[all_paths]`` section of your | 103 The extension can be configured using ``[all_paths]`` section of your |