developer.jelix.org is not used any more and exists only for
history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
Changes between Version 3 and Version 4 of en/patches
- Timestamp:
- Mar 23, 2010, 11:54:53 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
en/patches
v3 v4 39 39 When you have "review+", you can commit the patch in the repository if you have write acces, or a "commiter" will do it for you. 40 40 41 See [wiki:en/ mercurialto know the 'commit styles'].41 See [wiki:en/commit to know the 'commit styles']. 42 42 43 43 = Using Bitbucket and pull requesting = … … 47 47 So you can "fork" a jelix repository, commit into your clone, and request a pull. Add a comment on the corresponding ticket on developer.jelix.org to inform other contributors that you've made some changes. 48 48 49 Please don't propose tens of changesets/commits for a same ticket. Your clone should have only one commit, except if it is a big change. In this commit, each changeset should correspond to a specific step of the change. Don't hesitate to use the mq extension of Mercurial to track your changes before committing them into your clone on bitbucket. And of course, [wiki:en/ mercurialyour messages of changset should be well formatted].49 Please don't propose tens of changesets/commits for a same ticket. Your clone should have only one commit, except if it is a big change. In this commit, each changeset should correspond to a specific step of the change. Don't hesitate to use the mq extension of Mercurial to track your changes before committing them into your clone on bitbucket. And of course, [wiki:en/commit your messages of changset should be well formatted]. 50 50 51 51 ----