| 1 |
Alexander Berntsen wrote: |
| 2 |
> > There is no problem if github is only used for hosting, but if it |
| 3 |
> > is the primary point of contact, or if pull requests are accepted, |
| 4 |
> > then github is also writing to repositories, and merge commits are |
| 5 |
> > enforced for all external contributions. That does not scale at all. |
| 6 |
> |
| 7 |
> Users can still send patches via email even if the project is hosted |
| 8 |
> on GitHub. |
| 9 |
|
| 10 |
Of course, but 1. github users will not send email to a github |
| 11 |
project and 2. if pull requests are rejected then github is not |
| 12 |
the primary point of contact so then there is no problem. |
| 13 |
|
| 14 |
|
| 15 |
> And for the record I have not had problems with messy merges |
| 16 |
> when commiting pull requests. |
| 17 |
|
| 18 |
As I wrote: It works fine but doesn't scale; the mess is that you |
| 19 |
always get a merge commit, which is usually unneccessary for smaller |
| 20 |
contributions such as those from users, as opposed to larger ones |
| 21 |
spanning more commits and/or branches worked on over longer time |
| 22 |
from developers. |
| 23 |
|
| 24 |
|
| 25 |
//Peter |
Archives