procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; Minor addition to CONTRIBUTE

Browse source 
* CONTRIBUTE (http): Mention that doc fixes should always go to
the release branch.
This commit is contained in:
Eli Zaretskii 2016-10-04 08:59:37 +03:00
parent e1b2918c7c
commit ec6e4b9d1e
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CONTRIBUTE
View file

@ -189,6 +189,10 @@ If you are fixing a bug that exists in the current release, be sure to
commit it to the release branch; it will be merged to the master
branch later by the gitmerge function.
Documentation fixes (in doc strings, in manuals, and in comments)
should always go to the release branch, if the documentation to be
fixed exists and is relevant to the release-branch codebase.
However, if you know that the change will be difficult to merge to the
master (e.g., because the code on master has changed a lot), you can
apply the change to both master and branch yourself. It could also