From patchwork Wed Oct 9 17:47:12 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ryan Barnett X-Patchwork-Id: 281944 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from whitealder.osuosl.org (whitealder.osuosl.org [140.211.166.138]) by ozlabs.org (Postfix) with ESMTP id 6DFE42C00C2 for ; Thu, 10 Oct 2013 04:47:32 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 0981088AB3; Wed, 9 Oct 2013 17:47:31 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ck1LNfsbNFUe; Wed, 9 Oct 2013 17:47:29 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by whitealder.osuosl.org (Postfix) with ESMTP id 60C7B8651A; Wed, 9 Oct 2013 17:47:29 +0000 (UTC) X-Original-To: buildroot@lists.busybox.net Delivered-To: buildroot@osuosl.org Received: from whitealder.osuosl.org (whitealder.osuosl.org [140.211.166.138]) by ash.osuosl.org (Postfix) with ESMTP id DA75B1BF96B for ; Wed, 9 Oct 2013 17:47:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id D455687955 for ; Wed, 9 Oct 2013 17:47:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xt7mhuGcGFlG for ; Wed, 9 Oct 2013 17:47:28 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from secvs01.rockwellcollins.com (secvs01.rockwellcollins.com [205.175.225.240]) by whitealder.osuosl.org (Postfix) with ESMTPS id E11FD8651A for ; Wed, 9 Oct 2013 17:47:27 +0000 (UTC) Received: from nosuchhost.198.131.in-addr.arpa (HELO collinscrsmtp01.rockwellcollins.com) ([131.198.63.132]) by mail-virt.rockwellcollins.com with ESMTP; 09 Oct 2013 12:47:27 -0500 Received: from ares ([131.198.63.11]) by collinscrsmtp01.rockwellcollins.com (Lotus Domino Release 8.5.2FP2 HF162) with ESMTP id 2013100912472670-5837002 ; Wed, 9 Oct 2013 12:47:26 -0500 From: Ryan Barnett To: buildroot@busybox.net Date: Wed, 9 Oct 2013 12:47:12 -0500 Message-Id: <1381340833-29259-1-git-send-email-rjbarnet@rockwellcollins.com> X-Mailer: git-send-email 1.7.1 X-MIMETrack: Itemize by SMTP Server on CollinsCRSMTP01/CedarRapids/Collins/Rockwell(Release 8.5.2FP2 HF162|May 16, 2011) at 10/09/2013 12:47:26 PM, Serialize by Router on CollinsCRSMTP01/CedarRapids/Collins/Rockwell(Release 8.5.2FP2 HF162|May 16, 2011) at 10/09/2013 12:47:27 PM, Serialize complete at 10/09/2013 12:47:27 PM X-TNEFEvaluated: 1 Subject: [Buildroot] [PATCH v3 1/1] manual: update review process and patchwork X-BeenThere: buildroot@busybox.net X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: buildroot-bounces@busybox.net Sender: buildroot-bounces@busybox.net Adding more documentaiton based on discussion from the mailing list in regards the buildroot review process and how patchworks can be used to pull in patches for testing purposes. Mailing list discussion: http://lists.busybox.net/pipermail/buildroot/2013-September/078170.html Signed-off-by: Ryan Barnett --- v2 -> v3 * Changed 'a' to 'an' when preceeding +mbox+ (suggested by Thomas De Schampheleire) v1 -> v2 * Updated all references to patchwork to be Patchwork or Buildroot's Patchwork instead of a few misspellings (suggested by Thomas Petazzoni) * Added clarification that patchwork main use is for the Buildroot maintainer (suggested by Thomas Petazzoni) Signed-off-by: Ryan Barnett --- docs/manual/contribute.txt | 12 +++++++++++- docs/manual/get-involved.txt | 38 +++++++++++++++++++++++++++++++++++--- 2 files changed, 46 insertions(+), 4 deletions(-) diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt index 2b2783d..201685c 100644 --- a/docs/manual/contribute.txt +++ b/docs/manual/contribute.txt @@ -132,9 +132,15 @@ $ git format-patch --subject-prefix "PATCH v4" \ Reviewing/Testing patches ------------------------- +The review process for new patches is done over the mailing list. Once +a patch is submitted to the mailing list, other developers will provide +feedback to the patch via emails sent through the mailing list. + In the review process, do not hesitate to respond to patch submissions for remarks, suggestions or anything that will help everyone to -understand the patches and make them better. +understand the patches and make them better. Please use internet +style replies in plain text emails when responding to patch +submissions. Some tags are used to help following the state of any patch posted on the mailing-list: @@ -144,6 +150,10 @@ Acked-by:: Indicates that the patch can be committed. Tested-by:: Indicates that the patch has been tested. It is useful but not necessary to add a comment about what has been tested. +Buildroot's Patchwork website can be used to pull in patches for testing +purposes. Please see xref:apply-patches-patchwork[] for more +information on using Buildroot's Patchwork website to apply patches. + Autobuild --------- diff --git a/docs/manual/get-involved.txt b/docs/manual/get-involved.txt index 8515d34..aa319e2 100644 --- a/docs/manual/get-involved.txt +++ b/docs/manual/get-involved.txt @@ -55,11 +55,43 @@ using a code sharing website. Patchwork --------- -The Buildroot patch management interface is at +Patchwork is a web-based patch tracking system designed to facilitate +the contribution and management of contributions to an open-source +project. Patches that have been sent to a mailing list are \'caught' by +the system, and appear on a web page. Any comments posted that +reference the patch are appended to the patch page too. For more +information on Patchwork see +http://jk.ozlabs.org/projects/patchwork[]. + +Buildroot's Patchwork website is mainly for use by the Buildroot's +maintainer to ensure patches aren't missed. The website however, +exposes patches and their corresponding review comments in a clean +and concise web interface. + +The Buildroot patch management interface is available at http://patchwork.buildroot.org[]. -All patches and comments sent through the mailing list are -automatically indexed in http://patchwork.buildroot.org[patchwork]. +[[apply-patches-patchwork]] +Applying Patches from Patchwork +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Buildroot's Patchwork website main use for a developer is for pulling +in patches into their local git repository for testing purposes. + +When browsing patches in the patchwork management interface, an +mbox+ +link is provided at the top of the page. Copy this link address and +run the following commands: + +--------------------- +$ git checkout -b +$ wget -O - | git am +--------------------- + +Another option for applying patches is to create a bundle. A bundle is +a set of patches that you can group together using the patchwork +interface. Once the bundle is created and the bundle is made public, +you can copy the +mbox+ link for the bundle and apply the bundle +using the above commands. [[bugtracker]] Bugtracker