From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Chinner <david@fromorbit.com>
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 10:06:40 +1100 [thread overview]
Message-ID: <20190130100640.5c2512a4@canb.auug.org.au> (raw)
In-Reply-To: <20190129220802.GC4205@dastard>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
Hi Dave,
On Wed, 30 Jan 2019 09:08:02 +1100 Dave Chinner <david@fromorbit.com> wrote:
>
> Might be worth adding this to the boiler plate code:
>
> This can be fixed by adding the following to your ~/.gitconfig file:
>
> [core]
> abbrev = 12
Actually, since git v2.11 (released Nov 29, 2016), abbrev = auto (which
is the default) means that the default scales with the size of the
repository. For Linus' tree, that currently produces 12 digit commit
SHA1 abbreviations, but will probably soon become 13. So the best
currently, is to *not* set core.abbrev (or set it to something above 12
(for future robustness).
See
https://lore.kernel.org/lkml/20181220000112.24891-1-avarab@gmail.com/
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-29 23:06 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 [this message]
2019-01-29 23:43 ` Dave Chinner
2019-01-30 0:02 ` Stephen Rothwell
2019-01-30 0:38 ` Dave Chinner
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=20190130100640.5c2512a4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).