From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32497 invoked by alias); 9 Dec 2014 08:24:51 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 32485 invoked by uid 89); 9 Dec 2014 08:24:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,LIKELY_SPAM_BODY,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-ie0-f170.google.com Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 09 Dec 2014 08:24:48 +0000 Received: by mail-ie0-f170.google.com with SMTP id rd18so68496iec.15 for ; Tue, 09 Dec 2014 00:24:45 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.107.15.73 with SMTP id x70mr421814ioi.8.1418113485846; Tue, 09 Dec 2014 00:24:45 -0800 (PST) Received: by 10.50.235.38 with HTTP; Tue, 9 Dec 2014 00:24:45 -0800 (PST) Date: Tue, 09 Dec 2014 08:24:00 -0000 Message-ID: Subject: github... need suggestions from you. From: Bryan Hundven To: crossgcc maillist Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00039.txt.bz2 List, Prior to github, you'd 'git send-email' a change, it would be peer reviewed here, and once approved, it was applied. Post github, you fork the repo, make a branch, commit your changes, and approvals are done prior to merging the change. >From the test run I've done in the last couple of days, this hasn't worked out so well. And I'm looking for suggestions with this workflow. The major problem is that there is seemingly no way to have notifications of pull requests go to this mailing list: http://blog.wikichoon.com/2014/04/github-doesnt-support-pull-request.html So peer review must happen on github. I don't like this and I'm sure you'd like to review things too. The next problem is that my changes haven't been peer-reviewed, which lead to some mishaps with some linaro changes (which ultimately needs to be rewritten anyways, as there is a better way to manage that using kconfig options that are already in place). So, I need to eat the dog food and do pull requests myself. I'm not going to merge any changes until we can all agree on the workflow, so please post your thoughts on this topic. Thanks, -Bryan -- For unsubscribe information see http://sourceware.org/lists.html#faq