From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: devmanual moved to github
Date: Mon, 13 May 2013 14:28:31 +0100 [thread overview]
Message-ID: <20130513142831.79bd2e62@googlemail.com> (raw)
In-Reply-To: <20130513083205.6fc91266@sera-20.lan>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Mon, 13 May 2013 08:32:05 +0200
Ralph Sennhauser <sera@gentoo.org> wrote:
> On Mon, 13 May 2013 00:24:09 +0200
> Alexander Berntsen <alexander@plaimi.net> wrote:
> > On 13/05/13 00:21, Peter Stuge wrote:
> > > There is no problem if github is only used for hosting, but if it
> > > is the primary point of contact, or if pull requests are accepted,
> > > then github is also writing to repositories, and merge commits are
> > > enforced for all external contributions. That does not scale at
> > > all.
> >
> > Users can still send patches via email even if the project is hosted
> > on GitHub. And for the record I have not had problems with messy
> > merges when commiting pull requests.
>
> Once I was asked if I could look into a package. I spent a day writing
> a couple of ebuilds including fixing the build system of the target
> package. When I presented a first git-format-patch I was ask to do a
> github pull request instead. So I asked why not git-am? The answer was
> - don't be a *beep*. As a result the package never got fixed and I
> outright ignore any repo not hosted on Gentoo infra.
Once I found a bug in an ebuild. But unfortunately that ebuild was
stored in a CVS repo, so etc etc.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-05-13 13:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 11:32 [gentoo-dev] devmanual moved to github Markos Chandras
2013-05-12 13:12 ` Rich Freeman
2013-05-12 13:27 ` Peter Stuge
2013-05-12 15:02 ` Ben de Groot
2013-05-12 15:15 ` Markos Chandras
2013-05-12 15:12 ` Diego Elio Pettenò
2013-05-12 15:02 ` [gentoo-dev] " Duncan
2013-05-12 13:15 ` Ulrich Mueller
2013-05-12 15:04 ` Markos Chandras
2013-05-12 15:17 ` Peter Stuge
2013-05-12 15:48 ` Ulrich Mueller
2013-05-12 15:54 ` Markos Chandras
2013-05-12 16:08 ` Rich Freeman
2013-05-12 16:12 ` Michael Palimaka
2013-05-14 15:44 ` William Hubbs
2013-05-14 17:51 ` Rich Freeman
2013-05-12 16:55 ` Ulrich Mueller
2013-05-12 16:04 ` Mike Gilbert
2013-05-12 17:20 ` Peter Stuge
2013-05-12 17:32 ` Michael Palimaka
2013-05-12 18:24 ` Peter Stuge
2013-05-12 18:31 ` Michael Palimaka
2013-05-12 22:12 ` Alexander Berntsen
2013-05-12 22:21 ` Peter Stuge
2013-05-12 22:24 ` Alexander Berntsen
2013-05-12 22:37 ` Peter Stuge
2013-05-13 7:09 ` Alexander Berntsen
2013-05-12 22:38 ` W. Trevor King
2013-05-13 6:32 ` Ralph Sennhauser
2013-05-13 7:07 ` Alexander Berntsen
2013-05-13 7:40 ` Ralph Sennhauser
2013-05-13 7:47 ` Alexander Berntsen
2013-05-13 13:28 ` Ciaran McCreesh [this message]
2013-05-14 15:55 ` William Hubbs
2013-05-13 12:38 ` Greg KH
2013-05-13 12:42 ` Alexander Berntsen
2013-05-13 21:59 ` Duncan
2013-05-12 17:33 ` Theo Chatzimichos
2013-05-12 18:22 ` Peter Stuge
2013-05-12 19:18 ` [gentoo-dev] GitLab Feature-Set / Was: " sascha-ml
2013-05-14 13:59 ` Rich Freeman
2013-05-14 14:19 ` Peter Stuge
2013-05-14 14:40 ` Rich Freeman
2013-05-13 3:38 ` [gentoo-dev] " Arun Raghavan
2013-05-12 15:13 ` Richard Yao
2013-05-12 15:38 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130513142831.79bd2e62@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox