| 1 |
On Mon, 13 May 2013 08:32:05 +0200 |
| 2 |
Ralph Sennhauser <sera@g.o> wrote: |
| 3 |
> On Mon, 13 May 2013 00:24:09 +0200 |
| 4 |
> Alexander Berntsen <alexander@××××××.net> wrote: |
| 5 |
> > On 13/05/13 00:21, Peter Stuge wrote: |
| 6 |
> > > There is no problem if github is only used for hosting, but if it |
| 7 |
> > > is the primary point of contact, or if pull requests are accepted, |
| 8 |
> > > then github is also writing to repositories, and merge commits are |
| 9 |
> > > enforced for all external contributions. That does not scale at |
| 10 |
> > > all. |
| 11 |
> > |
| 12 |
> > Users can still send patches via email even if the project is hosted |
| 13 |
> > on GitHub. And for the record I have not had problems with messy |
| 14 |
> > merges when commiting pull requests. |
| 15 |
> |
| 16 |
> Once I was asked if I could look into a package. I spent a day writing |
| 17 |
> a couple of ebuilds including fixing the build system of the target |
| 18 |
> package. When I presented a first git-format-patch I was ask to do a |
| 19 |
> github pull request instead. So I asked why not git-am? The answer was |
| 20 |
> - don't be a *beep*. As a result the package never got fixed and I |
| 21 |
> outright ignore any repo not hosted on Gentoo infra. |
| 22 |
|
| 23 |
Once I found a bug in an ebuild. But unfortunately that ebuild was |
| 24 |
stored in a CVS repo, so etc etc. |
| 25 |
|
| 26 |
-- |
| 27 |
Ciaran McCreesh |
Archives