public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: devmanual moved to github
Date: Sun, 12 May 2013 18:38:48 -0400	[thread overview]
Message-ID: <20130512223848.GL23803@odin.tremily.us> (raw)
In-Reply-To: <51901689.10905@plaimi.net>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

On Mon, May 13, 2013 at 12:24:09AM +0200, Alexander Berntsen 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.

You can also merge pull requests locally and format them however you
like (including fast forward merges).  GitHub automatically closes the
PR when it's tip commit lands in the target branch.

My major gripe with PRs is folks sometimes add lots of good details to
the PR summary, and then have little one-line commit messages :p.  If
you can convince them to incorperate motivation, etc., in the commit
messages, than the fact that code came in via a PR is irrelevant.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-05-12 22:39 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 [this message]
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
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=20130512223848.GL23803@odin.tremily.us \
    --to=wking@tremily.us \
    --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