| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
The method coverts xml object as elementTree to dictionary.
Change-Id: Ia7eca3eb52a79979d7d1ee9d4ce1c842cc86e8ed
Signed-off-by: Bala.FA <barumuga@redhat.com>
Reviewed-on: https://cuckoo.blr.redhat.com:8443/22
|
| |
|
|
|
|
|
|
| |
Change-Id: Ideb9975c73ebc7c7339fa4aac354a974f1e3921e
Signed-off-by: Bala.FA <barumuga@redhat.com>
Reviewed-on: https://cuckoo.blr.redhat.com:8443/17
Reviewed-by: Sahina Bose <sabose@redhat.com>
Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Usage: rfc.sh [OPTION]... [ <REVIEWER> ]...
Options:
-a ask for Bug ID addition. This option is set by default for
non 'master' branches.
-b BRANCH use BRANCH to submitting patch. Default branch is 'master'.
-d dry run. Show what command to run.
-n do not fetch origin.
-t TOPIC use TOPIC to submitting patch.
-h display this help text and exit.
By default, BUGID is used as topic in patch submission. If TOPIC and
BUGID are used together, TOPIC gets used.
Examples:
# submit patch to master branch without reviewer
$ rfc.sh
# submit patch to master branch with reviewer
$ rfc.sh charlie@example.com
# submit patch to release-3.0 branch with topic "awesome feature" and
# reviewers charlie@example.com alice@example.com
$ rfc.sh -b release-3.0 -t "awesome feature" charlie@example.com alice@example.com
Change-Id: I6ca6f4ad70ea3a902c3415a12a12c3e46e79adef
Signed-off-by: Bala.FA <barumuga@redhat.com>
Reviewed-on: https://cuckoo.blr.redhat.com:8443/12
|
| |
|
|
|
| |
Change-Id: Ie8fdd046d111a4a46abe0e162985e833323bfd7d
Signed-off-by: Bala.FA <barumuga@redhat.com>
|
| |
|
