From: Stephen Hemminger <stephen@networkplumber.org>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: GIT workflow model to help solve some of the problems
Date: Thu, 22 Oct 2015 08:56:03 -0700 [thread overview]
Message-ID: <20151022085603.48dfcc66@xeon-e3> (raw)
In-Reply-To: <6E8EA5B4-B5B0-43A7-9229-7B00B575BDD3@intel.com>
The issue is the speed of review and merging.
Adding branching will make this worse not better, because there will
be more branches no one is looking at.
I made some concrete suggestions at the DPDK Userspace Summit
that would help if implemented.
prev parent reply other threads:[~2015-10-22 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 13:13 GIT workflow model to help solve some of the problems Wiles, Keith
2015-10-22 13:56 ` Richardson, Bruce
2015-10-22 14:03 ` Wiles, Keith
2015-10-22 15:56 ` Stephen Hemminger [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=20151022085603.48dfcc66@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=keith.wiles@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.