Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
adam.huang
Arm Trusted Firmware
Commits
92a7b0c3
Commit
92a7b0c3
authored
11 years ago
by
danh-arm
Browse files
Options
Download
Plain Diff
Merge pull request #34 from danh-arm/dh/new-integration-process
Update contributing.md with new integration process
parents
2eb01d34
7b5bf5c6
master
v2.5
v2.5-rc1
v2.5-rc0
v2.4
v2.4-rc2
v2.4-rc1
v2.4-rc0
v2.3
v2.3-rc2
v2.3-rc1
v2.3-rc0
v2.2
v2.2-rc2
v2.2-rc1
v2.2-rc0
v2.1
v2.1-rc1
v2.1-rc0
v2.0
v2.0-rc0
v1.6
v1.6-rc1
v1.6-rc0
v1.5
v1.5-rc3
v1.5-rc2
v1.5-rc1
v1.5-rc0
v1.4
v1.4-rc0
v1.3
v1.3_rc2
v1.3_rc1
v1.3-rc0
v1.2
v1.2-rc0
v1.1
v1.1-rc3
v1.1-rc2
v1.1-rc1
v1.1-rc0
v1.1-Juno-0.1
v1.0
v1.0-rc0
v0.4
v0.4-rc2
v0.4-rc1
v0.4-Juno-0.6-rc1
v0.4-Juno-0.6-rc0
v0.4-Juno-0.5
v0.4-Juno-0.5-rc1
v0.4-Juno-0.5-rc0
v0.4-Juno-0.4
v0.4-Juno-0.4-rc0
for-v0.4/05.22
for-v0.4/05.21
for-v0.4/05.20
for-v0.4-rc0
arm_cca_v0.2
arm_cca_v0.1
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
contributing.md
+15
-7
contributing.md
with
15 additions
and
7 deletions
+15
-7
contributing.md
View file @
92a7b0c3
...
...
@@ -78,16 +78,24 @@ Submitting Changes
*
Ensure we have your signed CLA.
*
Push your local changes to your fork of the repository.
*
Submit a [pull request] to arm-trusted-firmware.
*
The changes in the pull request will then undergo further review and
*
Submit a [pull request] to
the [
arm-trusted-firmware
]
`integration`
branch
.
*
The changes in the
[
pull request
]
will then undergo further review and
testing. Any review comments will be made as comments on the [pull
request]. This may require you to do some rework.
*
When the changes are accepted, ARM will integrate them.
*
To ensure a linear commit history, ARM will typically rebase the commits
locally before merging to the [arm-trusted-firmware]
`master`
branch. In
this case, the [pull request] will be closed rather than directly merged
on GitHub. If the rebase is not trivial, you may be asked to rebase the
commits yourself.
*
Typically, ARM will merge the [pull request] into the
`integration`
branch within the GitHub UI, creating a merge commit.
*
Please avoid creating merge commits in the [pull request] itself.
*
If the [pull request] is not based on a recent commit, ARM may rebase
it onto the
`master`
branch first, or ask you to do this.
*
If the [pull request] cannot be automatically merged, ARM will ask you
to rebase it onto the
`master`
branch.
*
After final integration testing, ARM will push your merge commit to the
`master`
branch. If a problem is found at this stage, the merge commit
will be removed from the
`integration`
branch and ARM will ask you to
create a new pull request to resolve the problem.
*
Please do not delete your topic branch until it is safely merged into
the
`master`
branch.
- - - - - - - - - - - - - - - - - - - - - - - - - -
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment
Menu
Projects
Groups
Snippets
Help