Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-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 B1E6A10B04 for ; Tue, 20 Jan 2015 15:20:12 +0000 (UTC) Received: (qmail 48438 invoked by uid 500); 20 Jan 2015 15:20:12 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 48365 invoked by uid 500); 20 Jan 2015 15:20:12 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 48352 invoked by uid 99); 20 Jan 2015 15:20:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2015 15:20:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anders.g.hammar@gmail.com designates 209.85.212.175 as permitted sender) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2015 15:20:07 +0000 Received: by mail-wi0-f175.google.com with SMTP id fb4so18282486wid.2 for ; Tue, 20 Jan 2015 07:19:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=HWOC/4NaEnXIwUlqlpd+V9iG+g5kEhBP6W+E3M5J0YE=; b=DoMU3MjE1dlpuwqNdDvQYsuqyv1sLdlK3HI2O+eepdWtqJJy2LruNmzQMPedqb9nVm KInAYlP3UWVY426ZjhBez2g+YpgLxqt6pr9Aj4O/dwV0ZES3uq6oO8CxxwdUZPEmfUcz A8ADeSKg/TUIh7/Qk06EieBpCCu0cfoy0mMU1S0BC5DaFPh8LI0oNa35Xe7Pc3Pqf50s RAeLAfctsKPwgtBV+7nMcK21EWyWdnja3JEz1K+mGeC86Og64FQQFoOMel+zYZ0orNpW rHDur7SWrLSJWqx8OJyTJrSWlC3g6wm6wcd6SlSUDjXLiQoZbCijgqGuq6Sp7iPCSbnn T7DA== MIME-Version: 1.0 X-Received: by 10.180.20.243 with SMTP id q19mr4557194wie.28.1421767141113; Tue, 20 Jan 2015 07:19:01 -0800 (PST) Sender: anders.g.hammar@gmail.com Received: by 10.194.176.230 with HTTP; Tue, 20 Jan 2015 07:19:01 -0800 (PST) In-Reply-To: References: Date: Tue, 20 Jan 2015 16:19:01 +0100 X-Google-Sender-Auth: LJzNF645gUUAiN4lVjOcjE9DtNg Message-ID: Subject: Re: Creating a patch for maven-pmd-plugin From: Anders Hammar To: Maven Developers List Content-Type: multipart/alternative; boundary=90e6ba18132c664a25050d16f579 X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba18132c664a25050d16f579 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable An svn patch is the preferred way for a plugin hosted in svn. http://maven.apache.org/guides/development/guide-maven-development.html /Anders On Tue, Jan 20, 2015 at 4:12 PM, wrote: > This may or may not be a "stupid question", but it's new territory for me > so I thought I would ask: > > I normally use Git for source control, so when I updated the > maven-pmd-plugin project, I just downloaded the source .zip file into a > new Git repo and made my changes. Now I need to create a patch to upload > my changes. Can I create a suitable patch using Git, or do I need to mov= e > all my work into Subversion and create the patch from there? > > > Tom Williamson > Senior Developer > O'Reilly Automotive > twilliamson32@oreillyauto.com > > > This communication and any attachments are confidential, protected by > Communications Privacy Act 18 USCS =C2=A7 2510, solely for the use of the > intended recipient, and may contain legally privileged material. If you > are not the intended recipient, please return or destroy it immediately. > Thank you. --90e6ba18132c664a25050d16f579--