| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA1
|
| 3 |
|
| 4 |
On Thu, 24 May 2012 13:52:32 -0400
|
| 5 |
Ian Stakenvicius <axs@g.o> wrote:
|
| 6 |
> > When the user has their tree up to how they want it, they can |
| 7 |
> > either send a pull request to another gentoo dev who also has a |
| 8 |
> > fork on github, or send a link to the commit via some medium ( bug |
| 9 |
> > tracker ? ) , and some dev can just add that as a remote, and |
| 10 |
> > merge/cherry-pick the commits they want.. |
| 11 |
> |
| 12 |
> ...is this something we (as the developer base) WANT non-dev's to be |
| 13 |
> able to do?? I would expect we'd want the tree to still be treated as |
| 14 |
> read-only-not-modifyable by the rest of the gentoo/linux community, |
| 15 |
> otherwise we're going to have a rather large mess on our hands |
| 16 |
> (multiple forks of the main tree != a uniform main tree + overlays, |
| 17 |
> the way it does now) |
| 18 |
|
| 19 |
That's only a problem if you don't merge things quickly. Encouraging
|
| 20 |
users to submit git format-patches or merge requests is a great way of
|
| 21 |
reducing developer workload.
|
| 22 |
|
| 23 |
- --
|
| 24 |
Ciaran McCreesh
|
| 25 |
-----BEGIN PGP SIGNATURE-----
|
| 26 |
Version: GnuPG v2.0.19 (GNU/Linux)
|
| 27 |
|
| 28 |
iEYEARECAAYFAk++eQMACgkQ96zL6DUtXhF4kgCfZkdR7RTvUUlFdTgdNkyDHwGK
|
| 29 |
NlgAoKgSUKEWN6WnrihawHkhhrPbJlv2
|
| 30 |
=8RdD
|
| 31 |
-----END PGP SIGNATURE----- |
Archives