I am aware of that. But it's a pain to do it. And then your local branch doesn't move forward when new stable releases come out. So I was suggesting we have a stable branch always available and known-good pointing to latest 1.X.X or 2.X.X release of latest stable 1.X or 2.X. It would also be friendly to maintenance programmers who want to submit patches to stable versions and encourage them to contribute stability fixes to DPDK just like Greg KH and the stable kernel guys do for the Long Term kernels.
Matthew. -- Sent from my mobile device. On October 22, 2014 6:43:36 AM PDT, Stephen Hemminger <stephen at networkplumber.org> wrote: >On Wed, 22 Oct 2014 00:00:58 -0700 >Matthew Hall <mhall at mhcomputing.net> wrote: > >> What I think git in general and DPDK in particular are missing is, >they have a >> tradition tags for releases, however I think this is broken because >you can't >> easily append more stuff to tages. > >In git tags and branches are almost the same thing. >You can easily create a local branch off of a tag.
