From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'Jason Gunthorpe'
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: release tarball top-level dir
Date: Fri, 20 Jan 2017 15:17:54 -0500 [thread overview]
Message-ID: <1484943474.43764.4.camel@redhat.com> (raw)
In-Reply-To: <01b101d2733b$f0179df0$d046d9d0$@opengridcomputing.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Fri, 2017-01-20 at 10:40 -0600, Steve Wise wrote:
> Hey all,
>
> Is this the intended top level dir?
>
> [root@stevo3 tmp]# tar tzf rdma-core-12.tar.gz
> rdma-core-rdma-core-12/
> rdma-core-rdma-core-12/.gitignore
> rdma-core-rdma-core-12/.travis.yml
>
No, but I don't know how to fix it just yet. The problem is that I
have to put rdma-core in the version tag or else the tarball is just
called v12.tar.gz, which really is not suitable. But I don't know how
to configure the git archive that github does on the back end to not
put the name in front of the tag when creating the tarball. I should
probably queue up a ticket with github's tech support to see what can
be done.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-20 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 16:40 release tarball top-level dir Steve Wise
2017-01-20 20:17 ` Doug Ledford [this message]
[not found] ` <1484943474.43764.4.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-21 8:26 ` Leon Romanovsky
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=1484943474.43764.4.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.