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.

Changes between Version 2 and Version 3 of en/patches


Ignore:
Timestamp:
Mar 23, 2010, 11:52:52 AM (11 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/patches

    v2 v3  
    3939When you have "review+", you can commit the patch in the repository if you have write acces, or a "commiter" will do it for you.
    4040
    41 See [wiki:en/subversion to know the 'commit styles'].
     41See [wiki:en/mercurial to know the 'commit styles'].
    4242
     43= Using Bitbucket and pull requesting =
    4344
     45An other way to provide a patch, is to work on bitbucket.org. Sources of Jelix are stored on Bitbucket.org. If you are registered on this site, Bitbucket allow you to publish a clone of a repository, and to commit changes to it. Then you can use the feature "pull request" of bitbucket to inform the owner of the "official" repository, to integrate your commit into his repository.
     46
     47So 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
     49Please 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/mercurial your messages of changset should be well formatted].
    4450
    4551----