Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 835F910E62 for ; Fri, 28 Jun 2013 19:56:43 +0000 (UTC) Received: (qmail 82713 invoked by uid 500); 28 Jun 2013 19:56:41 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 82608 invoked by uid 500); 28 Jun 2013 19:56:41 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 82600 invoked by uid 99); 28 Jun 2013 19:56:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jun 2013 19:56:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rarecactus@gmail.com designates 209.85.215.182 as permitted sender) Received: from [209.85.215.182] (HELO mail-ea0-f182.google.com) (209.85.215.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jun 2013 19:56:36 +0000 Received: by mail-ea0-f182.google.com with SMTP id d10so1242262eaj.41 for ; Fri, 28 Jun 2013 12:56:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=fOG220yf85XI7ZndShmRcdLl2ueqbTHgy3lv3kAm7fc=; b=mabjJIF2sHY40yI1W42tJxgppJye2wY8Qga7a8zWrSpWtHszJM523y08QLl+DSO6UO ZneZzxOyyH4/ihgHk5+RKV++TYfDfdyD2Uj1Izm7yy+1RpglXdNBuwMtyKE/uyx9+iw5 KKRmezfyYo3FTpiNo90OPC7p3eZ+v4y5FrukJrIN4oTUfZmnyz/kuuRQe3ujzVQObjBW ObOU+5aFJiC0/Dg6BsXZFjkleVrD0s5F+WfUBgLyOZHRisUHjoMFbCFgnbPC6bbb4PTE AZjE9zG2CF4maHESeHxLVNUS5VkoPLetrmfhBRUDCtKCJonrgN/anIcuU9hBP6pREkQ7 JBAg== MIME-Version: 1.0 X-Received: by 10.14.115.9 with SMTP id d9mr15127872eeh.87.1372449376089; Fri, 28 Jun 2013 12:56:16 -0700 (PDT) Sender: rarecactus@gmail.com Received: by 10.15.75.1 with HTTP; Fri, 28 Jun 2013 12:56:16 -0700 (PDT) In-Reply-To: References: Date: Fri, 28 Jun 2013 12:56:16 -0700 X-Google-Sender-Auth: fuWL-reJqVfLWFGHRrOmY7vX-lw Message-ID: Subject: Re: git line endings trouble since recent trunk From: Colin McCabe To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I think the fix for this is to set svn:eol-style to "native" on this file. It's set on many other files, just not on this one: cmccabe@keter:~/hadoopST/trunk> svn propget svn:eol-style ./hadoop-project-dist/README.txt native cmccabe@keter:~/hadoopST/trunk> svn propget svn:eol-style ./hadoop-hdfs-project/hadoop-hdfs/src/main/docs/releasenotes.html cmccabe@keter:~/hadoopST/trunk> It might also be a good idea to run dos2unix on it. I thought that in general we wanted to have 'LF' everywhere, so perhaps we should add this to the patch.sh script to prevent this from re-occurring. Colin On Fri, Jun 28, 2013 at 12:27 PM, Sandy Ryza wrote: > I haven't been able to find a solution. Just filed > https://issues.apache.org/jira/browse/HADOOP-9675. > > > On Fri, Jun 28, 2013 at 12:19 PM, Omkar Joshi wrote: > >> Sandy... did you fix this? any jira to track? me too facing same problem.. >> >> Thanks, >> Omkar Joshi >> *Hortonworks Inc.* >> >> >> On Fri, Jun 28, 2013 at 11:54 AM, Zhijie Shen >> wrote: >> >> > Have the same problem here, have to edit the patch manually to exclude >> the >> > changes in releasenotes.html >> > >> > >> > On Fri, Jun 28, 2013 at 11:01 AM, Sandy Ryza > > >wrote: >> > >> > > Has anybody else been having trouble with line endings since pulling >> > trunk >> > > recently? >> > > >> > > hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html >> > > shows up as modified even though I haven't touched it, and I can't >> check >> > it >> > > out or reset to a previous version to make that go away. The only >> thing >> > I >> > > can do to neutralize it is to put it in a dummy commit, but I have to >> do >> > > this every time I switch branches or rebase. >> > > >> > > This appears to have began after the release notes commit >> > > (8c5676830bb176157b2dc28c48cd3dd0a9712741), and must be due to a line >> > > endings change. >> > > >> > > -Sandy >> > > >> > >> > >> > >> > -- >> > Zhijie Shen >> > Hortonworks Inc. >> > http://hortonworks.com/ >> > >>