* CONTRIBUTE (Branches): Improve wording for back-ported commits.
This commit is contained in:
parent
f234fc2cb3
commit
ca947054e2
1 changed files with 6 additions and 4 deletions
10
CONTRIBUTE
10
CONTRIBUTE
|
@ -193,10 +193,12 @@ branch later.
|
|||
|
||||
However, if you know that the change will be difficult to merge to the
|
||||
trunk (eg because the trunk code has changed a lot), you can apply the
|
||||
change to both trunk and branch yourself. Indicate in the release
|
||||
branch commit log that there is no need to merge the commit to the
|
||||
trunk; start the commit message with "Backport:". gitmerge.el will
|
||||
then exclude that commit from the merge to trunk.
|
||||
change to both trunk and branch yourself. It could also happen that a
|
||||
change is cherry-picked from master to the release branch, and so
|
||||
doesn't need to be merged back. In these cases, indicate in the
|
||||
release branch commit log that there is no need to merge the commit to
|
||||
the trunk; start the commit message with "Backport:". gitmerge.el
|
||||
will then exclude that commit from the merge to trunk.
|
||||
|
||||
|
||||
** Other process information
|
||||
|
|
Loading…
Add table
Reference in a new issue