88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
to have their changes be merged into "official" branches by integrators.
For example, the Linux kernel team has a hierarchy of integrators with
Linus Torvalds at the root. Individual developers each have their own
private branches of the source tree into which they make their own changes.
They then encourage first-tier integrators to pull those changes. The
first-tier integrators merge together changes from multiple contributors
then try to get second-tier integrators to pull their branches. The
changes merge up the the hierarchy until (hopefully) they are pulled into
"Linus's branch", at which time they become part of the "official" Linux.
In Git, each branch is "owned" by the person who creates it and works
on it. The owner might pull changes from others, but the owner is always
in control of the branch. Branches are developer-centric.
Fossil, on the other hand, encourages a workflow where branches are
|
|
|
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
to have their changes be merged into "official" branches by integrators.
For example, the Linux kernel team has a hierarchy of integrators with
Linus Torvalds at the root. Individual developers each have their own
private branches of the source tree into which they make their own changes.
They then encourage first-tier integrators to pull those changes. The
first-tier integrators merge together changes from multiple contributors
then try to get second-tier integrators to pull their branches. The
changes merge up the hierarchy until (hopefully) they are pulled into
"Linus's branch", at which time they become part of the "official" Linux.
In Git, each branch is "owned" by the person who creates it and works
on it. The owner might pull changes from others, but the owner is always
in control of the branch. Branches are developer-centric.
Fossil, on the other hand, encourages a workflow where branches are
|