public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core V1 2/2] travis: Upload assets to github release
Date: Tue, 31 Jan 2017 10:57:41 +0200	[thread overview]
Message-ID: <20170131085741.GP6005@mtr-leonro.local> (raw)
In-Reply-To: <20170130211658.GC27111-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>

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

On Mon, Jan 30, 2017 at 02:16:58PM -0700, Jason Gunthorpe wrote:
> On Mon, Jan 30, 2017 at 10:19:53PM +0200, Leon Romanovsky wrote:
>
> > > > +if [[ $TRAVIS_TAG == v* ]] && [ "$TRAVIS_OS_NAME" = "linux" ]; then
> > > > +	# Let's create release for vX tags only.
> > > > +	git archive --prefix rdma-core/ --output rdma-core-$TRAVIS_TAG.tar.gz HEAD
> > >
> > > Should be
> > >
> > >
> > > I think..
> >
> > I have no opinion about that, because I'm not going to use this tar.gz file.
>
> Including the version in the directory is standard practice.

No problem, I pushed updated version.

>
> Jason

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

      parent reply	other threads:[~2017-01-31  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  6:23 [PATCH rdma-core V1 0/2] Create semi-automatic release process Leon Romanovsky
     [not found] ` <20170130062316.16268-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-30  6:23   ` [PATCH rdma-core V1 1/2] travis: Simplify travis config Leon Romanovsky
2017-01-30  6:23   ` [PATCH rdma-core V1 2/2] travis: Upload assets to github release Leon Romanovsky
     [not found]     ` <20170130062316.16268-3-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-30 17:09       ` Jason Gunthorpe
     [not found]         ` <20170130170956.GC29502-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-30 20:19           ` Leon Romanovsky
     [not found]             ` <20170130201953.GM6005-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-30 21:16               ` Jason Gunthorpe
     [not found]                 ` <20170130211658.GC27111-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-31  8:57                   ` Leon Romanovsky [this message]

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=20170131085741.GP6005@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox