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 6 and Version 7 of en/patches


Ignore:
Timestamp:
Jan 1, 2012, 10:07:21 PM (9 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/patches

    v6 v7  
    2525=== You create occasionnaly a patch ===
    2626
    27 The simplier way is to use "git diff". In the directory of your local copy of the repository, you should have made all your changes. When your changes are ok, just type:
     27The simplier way for a beginner is to use "git diff". In the directory of your local copy of the repository, you should have made all your changes. When your changes are ok, just type:
    2828
    2929  git diff > mypatch.diff
     
    3333If your modification has to be applied on stable branches, create the patch with the oldest branch.
    3434
    35 Submit the patch into a ticket on developer.jelix.org. The ticket can be an existing one, or perhaps you have to create it. Create/edit the ticket and attached the file. Then you have to request a review.  You should ask a review by setting the "review" field of the ticket to "review?". Then a reviewer will verify your patch. If it is ok, he will set "review+". If your patch needs some improvements, he will  set "review-" and then you will have to make improvements he asked and you will create a new patch, submit it on the ticket, ask "review?" and so on. 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.
     35Submit the patch into a ticket on developer.jelix.org. The ticket can be an existing one, or perhaps you have to create it. Create/edit the ticket and attached the file. Then you have to request a review.  Choose "ask a review" on the ticket. Then a reviewer will verify your patch. If it is ok, the ticket will be "reviewed". If your patch needs some improvements, it will be  "assigned" again and the reviewer will ask to make some improvements. Then create a new patch, submit it on the ticket, "ask a review" again and so on. When it is ok, you can commit the patch in the repository if you have write acces, or a "commiter" will do it for you.
    3636
    3737=== You are an active contributor ===
     
    7171Example:
    7272{{{
    73 git commit -u "Bob <bob@example.local>" -m "ticket #68987: added support of multiline tags in templates. r=laurent"
     73git commit -u "Bob <bob@example.local>" -m "ticket #68987 - added support of multiline tags in templates. r=laurent"
    7474}}}
    7575