From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: linux-next: Fixes tag needs some work in the xfs tree Date: Wed, 30 Jan 2019 11:38:18 +1100 Message-ID: <20190130003818.GG4205@dastard> References: <20190130075647.53e86078@canb.auug.org.au> <20190129220802.GC4205@dastard> <20190130100640.5c2512a4@canb.auug.org.au> <20190129234338.GF4205@dastard> <20190130110256.41722408@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190130110256.41722408@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell Cc: "Darrick J. Wong" , linux-xfs@vger.kernel.org, Linux Next Mailing List , Linux Kernel Mailing List , Christoph Hellwig List-Id: linux-next.vger.kernel.org On Wed, Jan 30, 2019 at 11:02:56AM +1100, Stephen Rothwell wrote: > Hi Dave, > > On Wed, 30 Jan 2019 10:43:38 +1100 Dave Chinner wrote: > > > > .... and in replying to correct me demonstrates the exact point I > > was making - that documenting what configuration should be used to > > avoid the warning acheives far more than just reporting an error. > > > > i.e. all those people who /don't follow git development/ and have > > working configs that pre-date the "auto mode" or it being made > > the default now know the correct way to configure their repository. > > Point taken. It now says: > > - SHA1 should be at least 12 digits long > Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11 > or later) just making sure it is not set (or set to "auto"). Wonderful! Cheers, Dave. -- Dave Chinner david@fromorbit.com