mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-15 10:30:25 -08:00
Merge from origin/emacs-25
4b347feClarify that doc fixes are okay in feature freeze01669adAvoid crashes when setting the cursorf2144eeRestore 'command-debug-status' functionalityec6e4b9; Minor addition to CONTRIBUTE
This commit is contained in:
commit
97046e811c
5 changed files with 18 additions and 4 deletions
|
|
@ -189,7 +189,13 @@ 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.
|
||||
|
||||
However, if you know that the change will be difficult to merge to the
|
||||
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. Doc
|
||||
fixes are always considered "safe" -- even when a release branch is in
|
||||
feature freeze, it can still receive doc fixes.
|
||||
|
||||
When 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
|
||||
happen that a change is cherry-picked from master to the release
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue