From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 154] Add a way to select what branch a patchset was meant for
Date: Tue, 05 Feb 2019 18:14:03 +0000 [thread overview]
Message-ID: <bug-154-149-rjmOfVfiC5@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-154-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=154
Jeremy Plsek (jplsek@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek@iol.unh.edu) ---
Logged in users can now select which branch/repo a patchset should be applied
to, and retry building, if an apply error or build error occurs.
Not all branch have been tested to rebuild properly. This may be because we
don't have a job set up yet (we will fix this when it occurs), or the branch is
not meant to be used for applying patchsets, such as tags.
This is essentially a more manual version of bug 166.
--
You are receiving this mail because:
You are the assignee for the bug.
parent reply other threads:[~2019-02-05 18:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-154-149@http.bugs.dpdk.org/>]
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=bug-154-149-rjmOfVfiC5@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).