DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrii <bearrailgun@gmail.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] how can I get a git version of Latest Major release? (18.02.1)
Date: Wed, 25 Apr 2018 17:02:07 +0300	[thread overview]
Message-ID: <CAJFD7HnG7eN3bY3EJd0W57Xq8rvJjPcyDzPnk81v9d0hnJbeig@mail.gmail.com> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA65E04D9C1@IRSMSX101.ger.corp.intel.com>

Nice.

Thanks Harry.

Yep I got 18.02.1 from dpdk-stable

Is that possible to have tags like  v18.02.1 in http://dpdk.org/git/dpdk
Because the only one I can get from it is v18.02
That would be great also if dpdk.org would provide some link to dpdk-stable
Because now it points only to http://dpdk.org/browse/dpdk/refs/
which shows only 18.02 as the latest release
So common user is just not able to get 18.02.1 from git anyhow if he is
just
browsing dpdk.org


On Wed, Apr 25, 2018 at 4:47 PM, Van Haaren, Harry <
harry.van.haaren@intel.com> wrote:

> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Andrii
> > Sent: Wednesday, April 25, 2018 2:45 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] how can I get a git version of Latest Major release?
> > (18.02.1)
> >
> > I could get only 18.02 tag, which is from February.
> > I want to see exactly which commits are in 18.02.1 and there is no such a
> > git tag
> > or github release etc.
> > Downloading 18.02.1 tarball without git history and comparing sources to
> > git tree seems quite stupid.
> > Also the question is why there is no such a branch or at least tag
> > which points to latest major? That seems strange.
> >
> > Thanks.
>
> Hi Andrii,
>
>
> All of the DPDK repos are available here:
> http://dpdk.org/browse
>
> Please see the stable repo for various table releases:
> http://dpdk.org/browse/dpdk-stable/
>
> You'll find tags, branches and more at the above location, eg:
> http://dpdk.org/browse/dpdk-stable/log/?h=v18.02.1
>
>
> Hope that helps, -Harry
>

  reply	other threads:[~2018-04-25 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 13:44 Andrii
2018-04-25 13:47 ` Van Haaren, Harry
2018-04-25 14:02   ` Andrii [this message]
2018-04-25 14:45     ` Thomas Monjalon
2018-04-25 14:47     ` Ferruh Yigit
2018-04-25 17:23       ` Andrii
2018-04-26 15:58         ` Thomas Monjalon
2018-04-26 16:15           ` Ferruh Yigit
2018-04-26 16:27             ` Thomas Monjalon
2018-04-26 19:25               ` Andrii
2018-04-26 21:02                 ` Thomas Monjalon

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=CAJFD7HnG7eN3bY3EJd0W57Xq8rvJjPcyDzPnk81v9d0hnJbeig@mail.gmail.com \
    --to=bearrailgun@gmail.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.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;
as well as URLs for NNTP newsgroup(s).