From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f179.google.com (mail-qc0-f179.google.com [209.85.216.179]) by dpdk.org (Postfix) with ESMTP id 3FC9368C0 for ; Tue, 18 Mar 2014 22:29:43 +0100 (CET) Received: by mail-qc0-f179.google.com with SMTP id m20so8778761qcx.10 for ; Tue, 18 Mar 2014 14:31:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FZx7PEjm7S9GsGMYp+YOFvheEpTF1XkZtwCIfKg3OhM=; b=TqlGTn4uM44kfU9BLmzAeUa1i6IKN2qtxA4LDcZ9QXuhBHvLn8yTzzwGIjs47cPHBX gSafJfyFJWkYknLNT7kGMIjz8RPrR69Ie/L1VEcWh6LEmutM1NDAQcOxhPZQ8iLwQPK4 P3aBRDcMahEmD2zxmHAVd/y1T+Mnr2OYabK5jAB4panKNn485KLK0PbChucYrd24TdiY iJE5sx5ujTs7lyHRtAutK5CVh7HHvdYggTU6bKlKtP2lMdu9YXnzkF0QeTJsMneBtMRy luGdh6zyFNfgi04XQ2Gpu/szLwUzVWrgmsVKQaaX7BRISV4FiXEWXDX1AeknlTUdaJji JIFw== X-Gm-Message-State: ALoCoQlttSkpw2iQqk+mzcrDhzWhUcgUMAnfSGeBOAUrkZ3CvNM4LQLjXP/HgPSIk0TIuesbXdxT MIME-Version: 1.0 X-Received: by 10.229.81.71 with SMTP id w7mr38913676qck.8.1395178274595; Tue, 18 Mar 2014 14:31:14 -0700 (PDT) Received: by 10.96.76.42 with HTTP; Tue, 18 Mar 2014 14:31:14 -0700 (PDT) X-Originating-IP: [128.107.239.234] In-Reply-To: <20140318135859.53fac97c@nehalam.linuxnetplumber.net> References: <20140318135859.53fac97c@nehalam.linuxnetplumber.net> Date: Tue, 18 Mar 2014 16:31:14 -0500 Message-ID: From: Kyle Mestery To: Stephen Hemminger Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] patchwork for dpdk.org? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Mar 2014 21:29:43 -0000 On Tue, Mar 18, 2014 at 3:58 PM, Stephen Hemminger < stephen@networkplumber.org> wrote: > Anybody considered setting up patchwork to track patches on this list? > > If not familiar, patchwork is a back end which maintainers and developers > can keep track of patches submitted and make sure of the status (accepted, > rejected, review, etc). > +1 for patchwork. In lieu of a more full-fledged CI/CD setup with Gerrit/Jenkins, patchwork is pretty nice.