From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: Fixes tag needs some work in the xfs tree
Date: Wed, 30 Jan 2019 11:38:18 +1100 [thread overview]
Message-ID: <20190130003818.GG4205@dastard> (raw)
In-Reply-To: <20190130110256.41722408@canb.auug.org.au>
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@fromorbit.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@fromorbit.com
next prev parent reply other threads:[~2019-01-30 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 20:56 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2019-01-29 22:08 ` Dave Chinner
2019-01-29 23:06 ` Stephen Rothwell
2019-01-29 23:43 ` Dave Chinner
2019-01-30 0:02 ` Stephen Rothwell
2019-01-30 0:38 ` Dave Chinner [this message]
2019-08-12 21:45 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2020-04-16 22:19 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2023-06-05 4:22 Stephen Rothwell
2023-09-19 7:25 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190130003818.GG4205@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).