comparison: doc/reference/libpurple/code_contributions.md
doc/reference/libpurple/code_contributions.md
- changeset 41424
- 5afbe5b72c49
- parent 41164
- d861b10105fb
equal
deleted
inserted
replaced
| 41418:ea740d03620b | 41424:5afbe5b72c49 |
|---|---|
| 242 which makes everyone's life easier. Also, the mainline repositories now auto | 242 which makes everyone's life easier. Also, the mainline repositories now auto |
| 243 publish, so if you do not selectively push commits, all of your draft commits | 243 publish, so if you do not selectively push commits, all of your draft commits |
| 244 will be published. You can name this additional clone whatever you like, but | 244 will be published. You can name this additional clone whatever you like, but |
| 245 using something like `pidgin-clean` is a fairly common practice. This makes it | 245 using something like `pidgin-clean` is a fairly common practice. This makes it |
| 246 easy for you to know that this clone is only meant for landing review requests, | 246 easy for you to know that this clone is only meant for landing review requests, |
| 247 and other admistrative work like updating the ChangeLog and COPYRIGHT files. | 247 and other administrative work like updating the ChangeLog and COPYRIGHT files. |
| 248 | 248 |
| 249 When you are ready to land a review request you need to make sure you are on | 249 When you are ready to land a review request you need to make sure you are on |
| 250 the proper branch. In most cases this will be the branch named ***default*** | 250 the proper branch. In most cases this will be the branch named ***default*** |
| 251 and can be verified by running the command `hg branch`. Next you need to make | 251 and can be verified by running the command `hg branch`. Next you need to make |
| 252 sure that your local copy is up to date. You can do this by running `hg pull | 252 sure that your local copy is up to date. You can do this by running `hg pull |
| 306 --no-backup --all`. This will return your repository to exactly what it was | 306 --no-backup --all`. This will return your repository to exactly what it was |
| 307 before the patch was applied. The `--no-backup` argument says to not save the | 307 before the patch was applied. The `--no-backup` argument says to not save the |
| 308 changes that you are reverting and the `--all` argument tells Mercurial to | 308 changes that you are reverting and the `--all` argument tells Mercurial to |
| 309 revert all files. | 309 revert all files. |
| 310 | 310 |
| 311 ### Cleaning up a Landed of Discarded Review Request | 311 ### Cleaning up a Landed or Discarded Review Request |
| 312 | 312 |
| 313 Whether or not your pull request has been accepted, you probably want to clean | 313 Whether or not your pull request has been accepted, you probably want to clean |
| 314 it up from your local repository. To do so, you need to update to a branch | 314 it up from your local repository. To do so, you need to update to a branch |
| 315 other than the branch you built it on. In the following example, we're going to | 315 other than the branch you built it on. In the following example, we're going to |
| 316 remove the branch named ***my-new-branch-name*** that we used to create a | 316 remove the branch named ***my-new-branch-name*** that we used to create a |
