public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Robertson <dan@dlrobertson.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, mtk.manpages@gmail.com,
	"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH 1/1] man2/fallocate.2: tfix documentation of shared blocks
Date: Sat, 3 Jul 2021 22:55:53 +0000	[thread overview]
Message-ID: <YODq+ZGxJLDxu5JY@dlrobertson.com> (raw)
In-Reply-To: <91a46f14-2337-e39a-386b-120a7b4ceb99@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

Alex,

On Sat, Jul 03, 2021 at 11:31:32PM +0200, Alejandro Colomar (man-pages) wrote:
> >>> On Sun, Jun 20, 2021 at 08:44:53PM -0400, Dan Robertson wrote:
> >>>> Fix a typo in the documentation of using fallocate to allocate shared
> >>>> blocks. The flag FALLOC_FL_UNSHARE should instead be documented as
> >>>> FALLOC_FL_UNSHARE_RANGE.
> >>>>
> >>>> Fixes: 07c7a6a35497 ("man2/fallocate.2: Document behavior with shared blocks")
> >>
> >> BTW, I can't find that commit hash in git.  I have that commit as
> >> 63a599c657d8.
> >>
> >> However, git doesn't fail...  It's weird.  Could you confirm that?
> > 
> > Gah! You are correct. My bad. I used copied the commit hash for the commit in
> > the kernel that introduced the FALLOC_FL_UNSHARE_RANGE flag. My bad.
> 
> I thought so, but I couldn't find that commit in Linus' tree either :/
> 
> [
> .../linux$ git log -1 07c7a6a35497
> fatal: ambiguous argument '07c7a6a35497': unknown revision or path not
> in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git <command> [<revision>...] -- [<file>...]'
> .../linux$ git log -1 07c7a6a35497 --
> fatal: bad revision '07c7a6a35497'
> .../linux$ cd ../man-pages/
> .../man-pages$ git log -1 07c7a6a35497
> .../man-pages$ git log -1 07c7a6a35497 --
> .../man-pages$
> ]
> 
> I can't understand that.  It fails in the kernel tree, but not in the
> man-pages tree.  But it doesn't find it in either.
> 
> It doesn't matter, but I'm curious...

Ah! Got it! 07c7a6a35497 is the tree hash for 63a599c657d8 in the man-pages
repo.

.../man-pages$ git rev-parse --short=12 63a599c657d8:
07c7a6a35497

I bet I copied the wrong hash from git blame in vim-fugitive when trying to
find the commit that first contained the typo.

> 
> > I can
> > submit a second version of the patch with the correct commit hash if you'd like.
> 
> No, don't worry; I fixed it.

Thanks!

 - Dan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-07-03 23:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21  0:44 [PATCH 0/1] man2/fallocate.2: Fix documentation of shared blocks Dan Robertson
2021-06-21  0:44 ` [PATCH 1/1] man2/fallocate.2: tfix " Dan Robertson
2021-06-21  4:25   ` Darrick J. Wong
2021-06-28 13:13     ` Dan Robertson
2021-07-03 18:20     ` Alejandro Colomar (man-pages)
2021-07-03 18:26     ` Alejandro Colomar (man-pages)
2021-07-03 20:09       ` Dan Robertson
2021-07-03 21:31         ` Alejandro Colomar (man-pages)
2021-07-03 22:55           ` Dan Robertson [this message]
2021-07-04 11:27             ` Alejandro Colomar (man-pages)
2021-07-03 18:18 ` [PATCH 0/1] man2/fallocate.2: Fix " Alejandro Colomar (man-pages)

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=YODq+ZGxJLDxu5JY@dlrobertson.com \
    --to=dan@dlrobertson.com \
    --cc=alx.manpages@gmail.com \
    --cc=djwong@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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