From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] development/integration branch?
Date: Wed, 22 Oct 2014 19:13:36 +0530 [thread overview]
Message-ID: <20141022191336.70174815@uryu.home.lan> (raw)
In-Reply-To: <20141022070058.GA6051@mhcomputing.net>
On Wed, 22 Oct 2014 00:00:58 -0700
Matthew Hall <mhall@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.
next prev parent reply other threads:[~2014-10-22 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:22 Marc Sune
2014-10-21 8:36 ` Richardson, Bruce
2014-10-21 8:46 ` Thomas Monjalon
2014-10-21 9:14 ` Marc Sune
2014-10-21 9:28 ` Thomas Monjalon
2014-10-21 9:38 ` Marc Sune
2014-10-21 13:50 ` Neil Horman
2014-10-22 7:00 ` Matthew Hall
2014-10-22 13:43 ` Stephen Hemminger [this message]
2014-10-22 15:54 ` Matthew Hall
2014-10-21 13:01 ` Stephen Hemminger
2014-10-23 9:19 ` Marc Sune
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=20141022191336.70174815@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).