From dev-return-3727-apmail-bloodhound-dev-archive=bloodhound.apache.org@bloodhound.apache.org Wed Nov 13 10:23:01 2013 Return-Path: X-Original-To: apmail-bloodhound-dev-archive@www.apache.org Delivered-To: apmail-bloodhound-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA8861017A for ; Wed, 13 Nov 2013 10:23:01 +0000 (UTC) Received: (qmail 37404 invoked by uid 500); 13 Nov 2013 10:23:00 -0000 Delivered-To: apmail-bloodhound-dev-archive@bloodhound.apache.org Received: (qmail 37374 invoked by uid 500); 13 Nov 2013 10:22:59 -0000 Mailing-List: contact dev-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@bloodhound.apache.org Delivered-To: mailing list dev@bloodhound.apache.org Received: (qmail 37356 invoked by uid 99); 13 Nov 2013 10:22:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 10:22:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saintger@gmail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qa0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 10:22:52 +0000 Received: by mail-qa0-f47.google.com with SMTP id w8so3625102qac.20 for ; Wed, 13 Nov 2013 02:22:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XAioPYq8R3DmuNrIdmBWH0t3dd3sVU4qRKDbJtS4l4s=; b=IrS0mal7i/f6sxGTOSX4Y8x+JXDwBSVX6g9kInUSBvX2wOBQvtMm2j3X9a0pTsMCwt OfSiWllmN0CMfmeMPAuvKa0XULXWi+9cjxbeFEPudEx16l7cCYBuNa402FVnqYUZ3uG/ 1KnKFg38Xssx7yMCkDRy1NYlMS1WhdCiKeuO0QR5RP1MfUa+TtfS4SGl8wLxiZooXq3U 8sBA4f4F/DbIm+mNRImHTt2IMJcoKhd1DQS36Df2HtJYkoAY2amVPqRWFtjy9jGIL4KN 3S33dsOyHtYJvbBW9SbSslwIULOkGoQgmIEU9Trba2xoKaFZx/6GS5XaaZUtz21VGaHk sodQ== MIME-Version: 1.0 X-Received: by 10.229.244.69 with SMTP id lp5mr64092334qcb.14.1384338152171; Wed, 13 Nov 2013 02:22:32 -0800 (PST) Received: by 10.96.187.137 with HTTP; Wed, 13 Nov 2013 02:22:32 -0800 (PST) In-Reply-To: References: Date: Wed, 13 Nov 2013 11:22:32 +0100 Message-ID: Subject: Re: Guidance needed to contribute to Bloodhound From: Saint Germain To: dev@bloodhound.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hello ! On 13 November 2013 11:10, Joachim Dreimann wrote: >> We can get the source from Subversion, from Github and Bitbucket and >> patches can be sent through patch/diff, github pull request and >> mercurial mq pull request. >> But what is the recommended method ? >> > > Code from Subversion and attaching patches/diffs to tickets. Github the > official mirror for the code. We haven't yet received pull requests there > so I'm not sure how we would best deal with them. > You can see on this ticket that I have tried using this method: https://issues.apache.org/bloodhound/ticket/694 However it got a little messy/confusing quite fast (unfortunately that patch touch a lot of files). And it is already broken against the current trunk. :-( As it is important to me, I am more than willing to maintain the patch against the current trunk, but I suppose that sending an updated patch to the ticket each time there is a needed change is a bit noisy. I am also willing to learn to use Github pull request if this is the official recommended way to manage the proposed patches. But if the official guidelines is to use Subversion and diff/patches, then I'll go this way and maintain my own mercurial-mq patches on my local repository. Thanks !