From: Mark Haywood <mark.haywood@oracle.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org
Subject: Re: buildlib/pandoc-prebuilt
Date: Wed, 4 Jan 2023 11:05:53 -0500 [thread overview]
Message-ID: <612e156e-d8c7-ee17-430d-9d6d85427a3f@oracle.com> (raw)
In-Reply-To: <Y7TF8EK/PXiwKRwU@ziepe.ca>
On 1/3/23 7:18 PM, Jason Gunthorpe wrote:
> On Tue, Jan 03, 2023 at 06:04:21PM -0500, Mark Haywood wrote:
>> I just extracted https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz
>> and noticed that buildlib/pandoc-prebuilt does not exist in v44.0. Is that
>> intentional?
> ?
>
> It looks OK:
>
> $ wget https://github.com/linux-rdma/rdma-core/releases/download/v44.0/rdma-core-44.0.tar.gz
> $ tar -tzf rdma-core-44.0.tar.gz | grep -i /pandoc-prebuilt/
> rdma-core-44.0/buildlib/pandoc-prebuilt/
> rdma-core-44.0/buildlib/pandoc-prebuilt/caaca7667f40fff2095c23c0f40c925f1ff3edea
> rdma-core-44.0/buildlib/pandoc-prebuilt/e2cfc53feeefa2927ad8741ae5964165b27d6aee
> rdma-core-44.0/buildlib/pandoc-prebuilt/971674ea9c99ebc02210ea2412f59a09a2432784
> rdma-core-44.0/buildlib/pandoc-prebuilt/241312b7f23c00b7c2e6311643a22e00e6eedaac
> [..]
I can't explain it. The one I pulled yesterday doesn't have them:
$ tar -tzf rdma-core-44.0.tar.gz.orig | grep -i /pandoc-prebuilt
rdma-core-44.0/buildlib/pandoc-prebuilt.py
The one today does:
$ tar -tzf rdma-core-44.0.tar.gz | grep -i /pandoc-prebuilt | less
rdma-core-44.0/buildlib/pandoc-prebuilt.py
rdma-core-44.0/buildlib/pandoc-prebuilt/
rdma-core-44.0/buildlib/pandoc-prebuilt/caaca7667f40fff2095c23c0f40c925f1ff3edea
rdma-core-44.0/buildlib/pandoc-prebuilt/e2cfc53feeefa2927ad8741ae5964165b27d6aee
[..]
I am sure it was user error on may part, though I don't see how.
Regardless, it's fine now, thanks.
Mark
> Jason
next prev parent reply other threads:[~2023-01-04 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 23:04 buildlib/pandoc-prebuilt Mark Haywood
2023-01-04 0:18 ` buildlib/pandoc-prebuilt Jason Gunthorpe
2023-01-04 16:05 ` Mark Haywood [this message]
2023-01-04 17:29 ` buildlib/pandoc-prebuilt Jason Gunthorpe
2023-01-04 18:42 ` buildlib/pandoc-prebuilt Leon Romanovsky
2023-01-04 19:18 ` buildlib/pandoc-prebuilt Mark Haywood
2023-01-05 5:53 ` buildlib/pandoc-prebuilt Leon Romanovsky
2023-01-06 18:38 ` buildlib/pandoc-prebuilt Mark Haywood
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=612e156e-d8c7-ee17-430d-9d6d85427a3f@oracle.com \
--to=mark.haywood@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@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