From: Zenaan Harkness <zen@freedbms.net>
To: git <git@vger.kernel.org>
Subject: release notes/ change number discrepancy ? - Documentation/RelNotes/2.10.0.txt "merge b738396..."
Date: Sun, 5 Feb 2017 13:21:56 +1100 [thread overview]
Message-ID: <20170205022156.GA19612@x220-a02> (raw)
Am I missing something in the following:
looking at Documentation/RelNotes/2.10.0.txt I see the following release
note (~line 35):
* "upload-pack" allows a custom "git pack-objects" replacement when
responding to "fetch/clone" via the uploadpack.packObjectsHook.
(merge b738396 jk/upload-pack-hook later to maint).
but when I run git show b738396 , I get the following:
commit b738396cfdcc276c0cde0c1a6462c5cc74ba7b76
Author: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Thu Jul 14 15:58:59 2016 +0200
mingw: fix regression in t1308-config-set
which seems to be completely unrelated. What am I missing please?
Thanks
Zenaan
next reply other threads:[~2017-02-05 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 2:21 Zenaan Harkness [this message]
2017-02-05 7:44 ` release notes/ change number discrepancy ? - Documentation/RelNotes/2.10.0.txt "merge b738396..." Junio C Hamano
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=20170205022156.GA19612@x220-a02 \
--to=zen@freedbms.net \
--cc=git@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