1 |
On 08/11/2015 04:10 PM, Alexis Ballier wrote: |
2 |
> On Tue, 11 Aug 2015 16:01:05 +0200 |
3 |
> Michał Górny <mgorny@g.o> wrote: |
4 |
> |
5 |
>> Dnia 2015-08-11, o godz. 15:52:16 |
6 |
>> Patrice Clement <monsieurp@g.o> napisał(a): |
7 |
>> |
8 |
>>> Hi there |
9 |
>>> |
10 |
>>> According to |
11 |
>>> https://wiki.gentoo.org/wiki/Gentoo_git_workflow#Branching_Model, |
12 |
>>> "there may be developer-specific, task-specific, project-specific |
13 |
>>> branches etc". As far as I understand, it means I can go and create |
14 |
>>> my own branch on the main repository and push it and it gets spread |
15 |
>>> all over the place. Is that correct? |
16 |
>>> |
17 |
>>> Could someone explain to me the rationale behind this decision? |
18 |
>>> |
19 |
>>> Truth to be told, I kinda dislike the fact any developer can do |
20 |
>>> this. |
21 |
>> |
22 |
>> As long as it's used with caution, I don't see a problem. |
23 |
> |
24 |
> Then we should define 'caution' I think :) |
25 |
> |
26 |
>> Of course it |
27 |
>> would be bad if everyone pushed branches for any minor change. |
28 |
>> However, if there is a long-term work going on a branch, I don't see |
29 |
>> a problem with keeping it public. |
30 |
> |
31 |
> Most, if not all, projects I've seen use forks for this. |
32 |
|
33 |
Blender does not, afaik. And I've seen a lot of projects doing that. The |
34 |
difference between e.g. "myremote/featurebranch" and |
35 |
"upstream/featurebranch" is just that someone has looked over |
36 |
"upstream/featurebranch" and that it requires pull requests to get stuff |
37 |
in (so the developer work happens in their developer forks, but the |
38 |
results still get into the same upstream branch). |
39 |
|
40 |
That would, for example, make sense for libressl. Since we basically |
41 |
just overwrite a lot of ebuilds to be able to test them with libressl |
42 |
patches. That is currently done with an overlay which always opens up |
43 |
the problem that we lack behind the tree and undesired openssl ebuilds |
44 |
leak in for the user, because of tree-overlay desync. |