| CONTRIBUTING.md (11901:70dda366c9aa) | CONTRIBUTING.md (11921:1b19c0bd7aa8) |
|---|---|
| 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. --- 172 unchanged lines hidden (view full) --- 181It is encouraged for the author of the patch and the submitter to add a 182Signed-off-by tag to the commit message. By adding this line, the contributor 183certifies the contribution is made under the terms of the Developer Certificate 184of Origin (DCO) [https://developercertificate.org/]. 185 186It is imperative that you use your real name and your real email address in 187both tags and in the author field of the changeset. 188 | 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. --- 172 unchanged lines hidden (view full) --- 181It is encouraged for the author of the patch and the submitter to add a 182Signed-off-by tag to the commit message. By adding this line, the contributor 183certifies the contribution is made under the terms of the Developer Certificate 184of Origin (DCO) [https://developercertificate.org/]. 185 186It is imperative that you use your real name and your real email address in 187both tags and in the author field of the changeset. 188 |
| 189For significant changes, authors are encouraged to add copyright information 190and their names at the beginning of the file. The main purpose of the author 191names on the file is to track who is most knowledgeable about the file (e.g., 192who has contributed a significant amount of code to the file). 193 |
|
| 189Note: If you do not follow these guidelines, the gerrit review site will 190automatically reject your patch. 191If this happens, update your changeset descriptions to match the required style 192and resubmit. The following is a useful git command to update the most recent 193commit (HEAD). 194 195 > git commit --amend 196 --- 136 unchanged lines hidden --- | 194Note: If you do not follow these guidelines, the gerrit review site will 195automatically reject your patch. 196If this happens, update your changeset descriptions to match the required style 197and resubmit. The following is a useful git command to update the most recent 198commit (HEAD). 199 200 > git commit --amend 201 --- 136 unchanged lines hidden --- |