From: Joe Perches <golf@perches.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Jacob Keller <jacob.e.keller@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: [PATCH] Documentation/process: hardcoded core.abbrev considered harmful!
Date: Tue, 15 Jan 2019 11:41:18 -0800 [thread overview]
Message-ID: <aa7337c0af524751d1f9d738b10d1e2d4e1199d8.camel@perches.com> (raw)
In-Reply-To: <20181220000112.24891-1-avarab@gmail.com>
On Thu, 2018-12-20 at 01:01 +0100, Ævar Arnfjörð Bjarmason wrote:
> Stop recommending that core.abbrev=12 be hardcoded when referring to
> kernel commits, and instead rely on the git's default abbreviation.
Nothing happened to this patch and there was no reply to
it as far as I can tell.
This may be sensible for future git versions, but perhaps
there should be a different abbrev control added and the
kernel should enable that.
> As an aside I have upcoming git.git patches so you'll be able to set
> core.abbbrev to e.g. +1 to get "13" now, "14" when it rolls over at
> ~16 million etc. Maybe that'll be a good fit for projects like
> linux.git that want more future-proof abbreviated SHAs than most.
Will '$ git config --get core.abbrev' return a specific
number in that case?
(not +1 and not blank as current if unspecified)
next prev parent reply other threads:[~2019-01-15 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 9:25 [PATCH] doc: update SubmittingPatches about the Fixes tag Jeff Kirsher
2018-12-20 0:01 ` [PATCH] Documentation/process: hardcoded core.abbrev considered harmful! Ævar Arnfjörð Bjarmason
2019-01-15 19:41 ` Joe Perches [this message]
2019-01-15 19:44 ` Keller, Jacob E
2019-01-30 0:18 ` Stephen Rothwell
2019-01-30 23:36 ` Frank Rowand
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=aa7337c0af524751d1f9d738b10d1e2d4e1199d8.camel@perches.com \
--to=golf@perches.com \
--cc=akpm@linux-foundation.org \
--cc=avarab@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®