Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 557A51082D for ; Tue, 1 Apr 2014 09:53:54 +0000 (UTC) Received: (qmail 48654 invoked by uid 500); 1 Apr 2014 09:53:46 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 48218 invoked by uid 500); 1 Apr 2014 09:53:45 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 48211 invoked by uid 99); 1 Apr 2014 09:53:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 09:53:44 +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 azuryyyu@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qc0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 09:53:38 +0000 Received: by mail-qc0-f176.google.com with SMTP id m20so10250310qcx.7 for ; Tue, 01 Apr 2014 02:53:17 -0700 (PDT) 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=TLZXs6fLrnDECR/Fjaz/wXinDvzGusicsoRdv8fpZHY=; b=BWlpG0f1KhDlI7FT7lUV8LU1mFsOuiY2SDDkWdUtwjM05bx0IxKxBUVWLo+KaKzplm G45hMbRVSBoYlYONi6NJdAbVc6ZpTNtUQhIIxLOU2HYBAy6f4+wr4UYaLcjEJKWdT3qX HM2xDYW/rXbPHILOGaeJ/Im94hK1yBXXzyEwsgKtctmbHKpZIsQCS4gAnqsxbPNF7R1g HnuWScXNbZbL8fh7bO709AphqcDoVlB3RGhm68BeR9St08RGGSIT/kdx3f7l2buBix97 iqylJJ5o9gA1HhHxA9lSp3d15FThsxeVhPHCzQwO7quhx0Pg9V+h2WiYR9B5MT57XMhd SQ8A== MIME-Version: 1.0 X-Received: by 10.140.19.212 with SMTP id 78mr12875962qgh.84.1396345997898; Tue, 01 Apr 2014 02:53:17 -0700 (PDT) Received: by 10.140.44.53 with HTTP; Tue, 1 Apr 2014 02:53:17 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Apr 2014 17:53:17 +0800 Message-ID: Subject: Re: patch format From: Azuryy Yu To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a1134effc306ffc04f5f823e5 X-Virus-Checked: Checked by ClamAV on apache.org --001a1134effc306ffc04f5f823e5 Content-Type: text/plain; charset=ISO-8859-1 There is no special patch format, just using svn diff or git diff to generate the patch, which depeds on your code repository. On Tue, Apr 1, 2014 at 5:14 PM, Avinash Kujur wrote: > > hello everyone, > > Is there any kind of specific format of the patch in which we need to > write the patch file. i submitted one patch but it got failed. i saw some > of the patches which were submitted previously. Is there sny kind of format > for patch? if it is, then please give me the link for format. > > Regards, > Avinash > --001a1134effc306ffc04f5f823e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
There is no special patch format, just using svn diff or g= it diff to generate the patch, which depeds on your code repository.
<= div class=3D"gmail_extra">

On Tue, Apr 1,= 2014 at 5:14 PM, Avinash Kujur <avinz50@gmail.com> wrote:
hello everyone,

Is there any kind of specific fo= rmat of the patch in which we need to write the patch file. i submitted one= patch but it got failed. i saw some of the patches which were submitted pr= eviously. Is there sny kind of format for patch? if it is, then please give= me the link for format.

Regards,
Avinash

--001a1134effc306ffc04f5f823e5--