| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 11/08/15 10:01 AM, Michał Górny wrote: |
| 5 |
> Dnia 2015-08-11, o godz. 15:52:16 Patrice Clement |
| 6 |
> <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 |
>> |
| 13 |
>> |
| 14 |
"there may be developer-specific, task-specific, project-specific branch |
| 15 |
es |
| 16 |
>> etc". As far as I understand, it means I can go and create my own |
| 17 |
>> branch on the main repository and push it and it gets spread all |
| 18 |
>> over the place. Is that correct? |
| 19 |
>> |
| 20 |
>> Could someone explain to me the rationale behind this decision? |
| 21 |
>> |
| 22 |
>> Truth to be told, I kinda dislike the fact any developer can do |
| 23 |
>> this. |
| 24 |
> |
| 25 |
> As long as it's used with caution, I don't see a problem. Of course |
| 26 |
> it would be bad if everyone pushed branches for any minor change. |
| 27 |
> However, if there is a long-term work going on a branch, I don't |
| 28 |
> see a problem with keeping it public. |
| 29 |
> |
| 30 |
|
| 31 |
Examples in particular I can think of for something like this being |
| 32 |
useful would be for, say, major EAPI-bump-related feature |
| 33 |
implementations (ie, EAPI5 and slot-operators/subslots), or major |
| 34 |
across-tree impementation changes like what we saw with the |
| 35 |
multilib-eclass porting. |
| 36 |
|
| 37 |
These are large projects touching most if not all ebuilds, that a |
| 38 |
great many developers would or should be involved in. Something like |
| 39 |
this could be done in a separately hosted repo instead of in the main |
| 40 |
gentoo repo, but then all developers would need to subscribe to this |
| 41 |
other repo, while having it in a branch in the main one i think would |
| 42 |
make it easier for everyone to get involved once they're ready, and |
| 43 |
would still allow the changes to stay out of the master branch until |
| 44 |
the project is ready to launch. |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
-----BEGIN PGP SIGNATURE----- |
| 52 |
Version: GnuPG v2 |
| 53 |
|
| 54 |
iF4EAREIAAYFAlXKEK8ACgkQAJxUfCtlWe35RwEAi2VkkJkCWXCh6tJhEKDbfmzY |
| 55 |
fP3rh20RURm84+8K2ysA/2u3dcTukXlGcLHW2xRSR/bjx5be1X+IL8A48bsqgujr |
| 56 |
=uppX |
| 57 |
-----END PGP SIGNATURE----- |
Archives