1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
<h2>all</h2>
The <code>all</code> command will let you perform (some) commands on
<em>all</em> of your repositories, and provides a way of finding all
of your repositories as well.
There are some commands you might especially want to perform on every
repository you've got, once in a while. <code> fossil all
</code> includes four of the most likely as sub-commands:
<code><a href="cmd_pull.wiki">pull</a></code>,
<code><a href="cmd_push.wiki">push</a></code>,
<code><a href="cmd_rebuild.wiki">rebuild</a></code> and
<code><a href="cmd_sync.wiki">sync</a></code>.
Follow the links to find out what each of those do, and then a moment
of thought will tell you why you might want to have them available for
all repositories.
Certainly you'll want your repositories all rebuilt when you upgrade
<b>fossil</b> after there has been a change in the repository
|
|
|
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
<h2>all</h2>
The <code>all</code> command will let you perform (some) commands on
<em>all</em> of your repositories, and provides a way of finding all
of your repositories as well.
There are some commands you might especially want to perform on every
repository you've got, once in a while. <code> fossil all
</code> includes four of the most likely as sub-commands:
[./cmd_pull.wiki | <code>pull</code>],
[./cmd_push.wiki | <code>push</code>],
[./cmd_rebuild.wiki | <code>rebuild</code>] and
[./cmd_sync.wiki | <code>sync</code>].
Follow the links to find out what each of those do, and then a moment
of thought will tell you why you might want to have them available for
all repositories.
Certainly you'll want your repositories all rebuilt when you upgrade
<b>fossil</b> after there has been a change in the repository
|
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
moving your repositories around. This is easy to do inadvertently if
you have a cavalier attitude about repos, but you'll know pretty
quickly that you've done it—many commands you try to use from
inside of a checkout won't work correctly. The <i>.fossil</i> file is
an <b>sqlite</b> db file which fossil uses to keeping track of
repository locations. Advice: if you move your repositories around,
let fossil know you did;
<code><a href="cmd_close.wiki">close</a></code> them before you move
them, and then <code><a href="cmd_open.wiki">open</a></code> them from
See also: <a href="cmd_pull.wiki">fossil pull</a>,
<a href="cmd_push.wiki">fossil push</a>,
<a href="cmd_rebuild.wiki">fossil rebuild</a>,
<a href="cmd_sync.wiki">fossil sync</a>,
<a href="cmd_open.wiki">fossil open</a>,
<a href="cmd_close.wiki">fossil close</a>,
<a href="reference.wiki">Reference</a>,
<b><a href="http://www.sqlite.org">sqlite</a></b>
|
|
|
|
|
|
|
|
|
|
|
|
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
moving your repositories around. This is easy to do inadvertently if
you have a cavalier attitude about repos, but you'll know pretty
quickly that you've done it—many commands you try to use from
inside of a checkout won't work correctly. The <i>.fossil</i> file is
an <b>sqlite</b> db file which fossil uses to keeping track of
repository locations. Advice: if you move your repositories around,
let fossil know you did;
[./cmd_close.wiki | <code>close</code>] them before you move
them, and then [./cmd_open.wiki | <code>open</code>] them from
their new locations.
See also: [./cmd_pull.wiki | fossil pull],
[./cmd_push.wiki | fossil push],
[./cmd_rebuild.wiki | fossil rebuild],
[./cmd_sync.wiki | fossil sync],
[./cmd_open.wiki | fossil open],
[./cmd_close.wiki | fossil close],
[./reference.wiki | Reference],
[http://www.sqlite.org | <b>SQLite</b>]
|