+and are struggling with some concepts, please ask for help on the
8
+[Fossil Forum][1]. The people who write this document are intimately
9
+familiar with Fossil and less It is difficult for
10
+ initimately familiar
11
+with Git ## Help Improve This Document
12
+
13
+ experience, and you are new to Fossil
14
+and are struggling with some concepts, please ask for help on the
15
+[Fossil Forum][1]. The people who write this document are intimately
16
+familiar with Fossil and less It is difficult for
17
+ initimately familiar
18
+with Git and less familiar with Fossil. AskingForum
19
+will help us tSpecific suggestions on how to improve this document are also welcomed,
20
+of course.
21
+
22
+
23
+
24
+## <a
25
+----in
26
+which is stored. A(See for more Fossil terms of art that may
27
+be unfamiliar to a Git user.)moreFossil can operate in the Git modeit can(Note that Ffor you as
28
+Git d.
29
+
30
+
31
+## Help Improve This Document
32
+
33
+ experience, and you are new to Fossil
34
+and are struggling with some concepts, please ask for help on the
35
+[Fossil Forum][1]. The people who write this document are intimately
36
+familiar with Fossil and less It is difficult for
37
+ initimately familiar
38
+with Git and less familiar with Fossil. AskingForum
39
+will help us tSpecific suggestions on how to improve this document are also welcomed,
40
+of course.
41
+
42
+
43
+
44
+## <a
45
+----in
46
+which eased -e This Document
47
+ more Fossil terms of art that may
48
+be unfamiliar to a Git user.)moreFossil can operate in the Git modeit can(Note that Ffor you as
49
+Gfter-The-Fact
50
+
51
+Fossil per“open” command][open], which hwhen you commit using
52
+the "`--branch` _BRANCH-NAME_" command-line option. he
53
+[Fossil Forum][1]. The pecommium][1]. The people who wrIt is not necessary to create branches ahead of time, as in Git, though
54
+that is allowedme concepts, please branch new`prove This Document
55
+
56
+ experience, and you are new to Fossil
57
+and are struggling with some concepts, please ask for help on the
58
+[Fossil Forum][1]. The people who wrfic suggestions on how to ik2p@40C,L:,
59
+so what you want is3d@43a,G6@47E,l@4NQ,2:isUF@4O9,2b@4rP,3X@4u0,6q:Unlike Git, Fossil’s “clone and open� call here that isn’t
60
+needed in the Git case. This is an indirect reflection of Fossil’s
61
+[multiple working directories](#mwd) design philosophy: its
62
+[`open` command][open] requires that you either issue it in an empty
63
+directory or one containing a prior closed check-out. In exchange for
64
+this extra command, we getS@5Bc,1s:
65
+[superior handling][shwmd] of multiple workingy can reside
66
+h fromS@4xk,3X:
67
+comma hierarchy with the check-out as with Git, but it
68
+is more common to putopen� call herein a separate directory.
69
+
70
+[2]:
71
+Fossil repositories are a single file, rather than being a directory
72
+hierarsitory file
73
+rn to parenwillI, but acum[1]. but it is best to usence, and you are new to Fossil
74
+and are struggling all branches, all wiki, all tickets,Fossil -i,3m@3uC,3:—S@3xx,1:,1W@3yS,P:maybe one part-day a week2p@40C,L:ne and open� - everything.
75
+�s
76
+[multiple working directories](#mwd) design philosophy: its
77
+[`open` command][open] requires that you either issue it in an empty
78
+directory or one containing a prior closed check-out. In exchange for
79
+this extra command, we getS@5Bc,1s:
80
+[superior handling][shwmd] of multiple working directories. To get the
81
+full power of this feature, you’d switch fromS@4xk,3X:
82
+command form to the separate clone-and-open form shown in
83
+[the quick start guide][qs], which adds one more command.
84
+
85
+We can’t spin the longer final command as a trade-off giving us extra
86
+power, though: the simple fact is, 5f@50N,1:KU@56j## T[2]:
87
+Fossil repositornge for
88
+this extra command, we getS@5Bc,1s:
89
+[superior handling][shwmd] of multiple workingy can reside
90
+h fromS@4xk,3X:
91
+comma hierarchy with the check-out as with Git, but it
92
+is more common to putopen� call herein a separate directory.
93
+
94
+[2]:
95
+Fossil repositories are a single file, rather than being a directory
96
+hierarchy as with the "` parenwillI, but acum[1]. .
97
+This is a [, all wiki, all tickets,Fo open� call here that isn�the [Rebase Considered Harmndirect reflection of Fossilflection of Fossil’s
98
+[m�s
99
+[multiple working directories](#mwd) design philosophy: its
100
+[`open` command][open] requires that you either issue it in an empty
101
+directory or one containing a prior closed check-out. In exchange for
102
+this extra command, we getS@5Bc,1s:
103
+[superior handling][shwmd] of multiple working directories. To get the
104
+full power of this feature, you’d switch fromS@4xk,3X:
105
+command form to the separate clone-and-open form show
106
+
107
+## Only One "origin" At A Time
108
+
109
+A extra command, we only keeps track of one "origin" server at a time.
110
+If you specify a new "origin" it forgets the previous one. Use the
111
+"`fossil remote`" command to see or change the "origin".
112
+
113
+Fossil uses a very different sync protocol than Git, so ifor recording cherry-picks in the Git file
114
+format, so you have to talk about the cTbut do not actually
115
+dn’t use `--set-upstream/-u` hercause we didn’t use `--set-upstream/-u` here, we have to name the
116
+“worwork” origin explicitly in these commands. (This also shows Git�have. (This also shows Git’s
117
+unwillingness to sync branch names, covered el
118
+Yes, this is goofy. It needs to be changed. Unfortunately there are
119
+script compati
--- a/www/gitusers.md
+++ b/www/gitusers.md
@@ -0,0 +1,119 @@
--- a/www/gitusers.md
+++ b/www/gitusers.md
@@ -0,0 +1,119 @@
1
.
2
3
4
## Help Improve This Document
5
6
experience, and you are new to Fossil
7
and are struggling with some concepts, please ask for help on the
8
[Fossil Forum][1]. The people who write this document are intimately
9
familiar with Fossil and less It is difficult for
10
initimately familiar
11
with Git ## Help Improve This Document
12
13
experience, and you are new to Fossil
14
and are struggling with some concepts, please ask for help on the
15
[Fossil Forum][1]. The people who write this document are intimately
16
familiar with Fossil and less It is difficult for
17
initimately familiar
18
with Git and less familiar with Fossil. AskingForum
19
will help us tSpecific suggestions on how to improve this document are also welcomed,
20
of course.
21
22
23
24
## <a
25
----in
26
which is stored. A(See for more Fossil terms of art that may
27
be unfamiliar to a Git user.)moreFossil can operate in the Git modeit can(Note that Ffor you as
28
Git d.
29
30
31
## Help Improve This Document
32
33
experience, and you are new to Fossil
34
and are struggling with some concepts, please ask for help on the
35
[Fossil Forum][1]. The people who write this document are intimately
36
familiar with Fossil and less It is difficult for
37
initimately familiar
38
with Git and less familiar with Fossil. AskingForum
39
will help us tSpecific suggestions on how to improve this document are also welcomed,
40
of course.
41
42
43
44
## <a
45
----in
46
which eased -e This Document
47
more Fossil terms of art that may
48
be unfamiliar to a Git user.)moreFossil can operate in the Git modeit can(Note that Ffor you as
49
Gfter-The-Fact
50
51
Fossil per“open” command][open], which hwhen you commit using
52
the "`--branch` _BRANCH-NAME_" command-line option. he
53
[Fossil Forum][1]. The pecommium][1]. The people who wrIt is not necessary to create branches ahead of time, as in Git, though
54
that is allowedme concepts, please branch new`prove This Document
55
56
experience, and you are new to Fossil
57
and are struggling with some concepts, please ask for help on the
58
[Fossil Forum][1]. The people who wrfic suggestions on how to ik2p@40C,L:,
59
so what you want is3d@43a,G6@47E,l@4NQ,2:isUF@4O9,2b@4rP,3X@4u0,6q:Unlike Git, Fossil’s “clone and open� call here that isn’t
60
needed in the Git case. This is an indirect reflection of Fossil’s
61
[multiple working directories](#mwd) design philosophy: its
62
[`open` command][open] requires that you either issue it in an empty
63
directory or one containing a prior closed check-out. In exchange for
64
this extra command, we getS@5Bc,1s:
65
[superior handling][shwmd] of multiple workingy can reside
66
h fromS@4xk,3X:
67
comma hierarchy with the check-out as with Git, but it
68
is more common to putopen� call herein a separate directory.
69
70
[2]:
71
Fossil repositories are a single file, rather than being a directory
72
hierarsitory file
73
rn to parenwillI, but acum[1]. but it is best to usence, and you are new to Fossil
74
and are struggling all branches, all wiki, all tickets,Fossil -i,3m@3uC,3:—S@3xx,1:,1W@3yS,P:maybe one part-day a week2p@40C,L:ne and open� - everything.
75
�s
76
[multiple working directories](#mwd) design philosophy: its
77
[`open` command][open] requires that you either issue it in an empty
78
directory or one containing a prior closed check-out. In exchange for
79
this extra command, we getS@5Bc,1s:
80
[superior handling][shwmd] of multiple working directories. To get the
81
full power of this feature, you’d switch fromS@4xk,3X:
82
command form to the separate clone-and-open form shown in
83
[the quick start guide][qs], which adds one more command.
84
85
We can’t spin the longer final command as a trade-off giving us extra
86
power, though: the simple fact is, 5f@50N,1:KU@56j## T[2]:
87
Fossil repositornge for
88
this extra command, we getS@5Bc,1s:
89
[superior handling][shwmd] of multiple workingy can reside
90
h fromS@4xk,3X:
91
comma hierarchy with the check-out as with Git, but it
92
is more common to putopen� call herein a separate directory.
93
94
[2]:
95
Fossil repositories are a single file, rather than being a directory
96
hierarchy as with the "` parenwillI, but acum[1]. .
97
This is a [, all wiki, all tickets,Fo open� call here that isn�the [Rebase Considered Harmndirect reflection of Fossilflection of Fossil’s
98
[m�s
99
[multiple working directories](#mwd) design philosophy: its
100
[`open` command][open] requires that you either issue it in an empty
101
directory or one containing a prior closed check-out. In exchange for
102
this extra command, we getS@5Bc,1s:
103
[superior handling][shwmd] of multiple working directories. To get the
104
full power of this feature, you’d switch fromS@4xk,3X:
105
command form to the separate clone-and-open form show
106
107
## Only One "origin" At A Time
108
109
A extra command, we only keeps track of one "origin" server at a time.
110
If you specify a new "origin" it forgets the previous one. Use the
111
"`fossil remote`" command to see or change the "origin".
112
113
Fossil uses a very different sync protocol than Git, so ifor recording cherry-picks in the Git file
114
format, so you have to talk about the cTbut do not actually
115
dn’t use `--set-upstream/-u` hercause we didn’t use `--set-upstream/-u` here, we have to name the
116
“worwork” origin explicitly in these commands. (This also shows Git�have. (This also shows Git’s
117
unwillingness to sync branch names, covered el
118
Yes, this is goofy. It needs to be changed. Unfortunately there are