| CONTRIBUTING.md (12883:9a34863049c2) | CONTRIBUTING.md (13398:2dc39228c2b5) |
|---|---|
| 1Authors: Jason Lowe-Power 2 Andreas Sandberg 3 Steve Reinhardt 4 5If you've made changes to gem5 that might benefit others, we strongly encourage 6you to contribute those changes to the public gem5 repository. There are 7several reasons to do this: 8 * Share your work with others, so that they can benefit from new functionality. --- 63 unchanged lines hidden (view full) --- 72 +-------------+ 73 74After creating your change to gem5, you can post a review on our Gerrit 75code-review site: https://gem5-review.googlesource.com. Before being able to 76submit your code to the mainline of gem5, the code is reviewed by others in the 77community. Additionally, the maintainer for that part of the code must sign off 78on it. 79 | 1Authors: Jason Lowe-Power 2 Andreas Sandberg 3 Steve Reinhardt 4 5If you've made changes to gem5 that might benefit others, we strongly encourage 6you to contribute those changes to the public gem5 repository. There are 7several reasons to do this: 8 * Share your work with others, so that they can benefit from new functionality. --- 63 unchanged lines hidden (view full) --- 72 +-------------+ 73 74After creating your change to gem5, you can post a review on our Gerrit 75code-review site: https://gem5-review.googlesource.com. Before being able to 76submit your code to the mainline of gem5, the code is reviewed by others in the 77community. Additionally, the maintainer for that part of the code must sign off 78on it. 79 |
| 80Contributing long-lived feature branches 81---------------------------------------- 82Oftentimes users or institutions add features that are necessarily complex, 83and require many changes on long-lived feature branches. In this case, 84maintaining a perfect history where all changes work individually is infeasible. 85When contributing long-lived feature branches back to gem5's public repository 86users may merge entire long-lived branches into a single changeset and contribute 87their code back as long as 1) the changes have been reviewed by the maintainer 882) the maintainer agrees to allow such a change, and 3) the changes are passing 89the public tests. Changes that affect common code (outside of a specific 90maintainer's purview) will still need to follow the standard gem5 protocol. 91 92 |
|
| 80Cloning the gem5 repo to contribute 81=================================== 82 83If you plan on contributing, it is strongly encouraged for you to clone the 84repository directly from our gerrit instance at 85https://gem5.googlesource.com/. 86 87To clone the master gem5 repository: --- 266 unchanged lines hidden --- | 93Cloning the gem5 repo to contribute 94=================================== 95 96If you plan on contributing, it is strongly encouraged for you to clone the 97repository directly from our gerrit instance at 98https://gem5.googlesource.com/. 99 100To clone the master gem5 repository: --- 266 unchanged lines hidden --- |