From: Thomas Monjalon <thomas@monjalon.net>
To: Andrii <bearrailgun@gmail.com>
Cc: dev@dpdk.org, "Van Haaren, Harry" <harry.van.haaren@intel.com>,
web@dpdk.org
Subject: Re: [dpdk-web] [dpdk-dev] how can I get a git version of Latest Major release? (18.02.1)
Date: Wed, 25 Apr 2018 16:45:27 +0200 [thread overview]
Message-ID: <2070062.patfpU1Hje@xps> (raw)
In-Reply-To: <CAJFD7HnG7eN3bY3EJd0W57Xq8rvJjPcyDzPnk81v9d0hnJbeig@mail.gmail.com>
Hi,
25/04/2018 16:02, Andrii:
> 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
No, the main repo is not managing stable branches.
You will have backports and stable release tags only in dpdk-stable.
But you can have both in the directory by using "git remote add".
> 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
Yes the webpage could point explicitly to it.
> So common user is just not able to get 18.02.1 from git anyhow if he is
> just
> browsing dpdk.org
Note that browsing allows to find it:
http://dpdk.org/browse/
You will find also a repo dpdk-web to send a patch for such change on the
website. The mailing list is web@dpdk.org (Cc'ed).
> 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
> >
>
parent reply other threads:[~2018-04-25 14:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAJFD7HnG7eN3bY3EJd0W57Xq8rvJjPcyDzPnk81v9d0hnJbeig@mail.gmail.com>]
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=2070062.patfpU1Hje@xps \
--to=thomas@monjalon.net \
--cc=bearrailgun@gmail.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=web@dpdk.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;
as well as URLs for NNTP newsgroup(s).