Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 D69DA1087B for ; Tue, 1 Apr 2014 10:04:36 +0000 (UTC) Received: (qmail 75182 invoked by uid 500); 1 Apr 2014 10:04:27 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 74844 invoked by uid 500); 1 Apr 2014 10:04:26 -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 74831 invoked by uid 99); 1 Apr 2014 10:04:25 -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 10:04:24 +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.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qa0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 10:04:19 +0000 Received: by mail-qa0-f54.google.com with SMTP id w8so9402014qac.27 for ; Tue, 01 Apr 2014 03:03:58 -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=L3CYLi+J43e3wP4Lgc7DlU0q6oiK0nTG4N4HlTV5p3w=; b=C6Q/CHwlZrrl+3h1uE4P5vJ/Yj5Aenj5/rJO1i14i3Yhe6DKnMrvbl62QPOGi7zXxw UiawnxxQAer7q/aagLJwRfkCObgFFLUwgH5xEytE/WoyMv+qiSyJuXg1pK0PiOCxiDNW DXGWtpocjkCGoVRYONu4wmEXRZ3PDVWicv+YVyUmNDdD2f8uAo+Dea42CATlA6oiJSb1 8Ln5rABsP6HRp3M0DuKNvGP9Of8+KUtFPjYRhQRF74gGWp/Js5g1rJ/9EtSu6nGq0WP9 gfFikVYAiQIhH2pR4TVcsVF7g/G4nCG3pLM9yEOqTKc/j/BomtMa/MxE0Eq3+i3pxZiS ffZw== MIME-Version: 1.0 X-Received: by 10.224.134.194 with SMTP id k2mr17683388qat.5.1396346638764; Tue, 01 Apr 2014 03:03:58 -0700 (PDT) Received: by 10.140.44.53 with HTTP; Tue, 1 Apr 2014 03:03:58 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Apr 2014 18:03:58 +0800 Message-ID: Subject: Re: patch format From: Azuryy Yu To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c2c3466310c204f5f8496f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2c3466310c204f5f8496f 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 > --001a11c2c3466310c204f5f8496f 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

--001a11c2c3466310c204f5f8496f--