[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190130003818.GG4205@dastard>
Date: Wed, 30 Jan 2019 11:38:18 +1100
From: Dave Chinner <david@...morbit.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Darrick J. Wong" <darrick.wong@...cle.com>,
linux-xfs@...r.kernel.org,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>
Subject: Re: linux-next: Fixes tag needs some work in the xfs tree
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 <david@...morbit.com> 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@...morbit.com
Powered by blists - more mailing lists