mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-03-26 08:41:47 -07:00
Adding advice about what to put in the version branch description.
Copied from Perforce Change: 190709 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
17b6ff61ca
commit
9c84be01ad
1 changed files with 5 additions and 1 deletions
|
|
@ -97,9 +97,13 @@ Run the script ``tool/branch``, passing the options:
|
|||
* ``-p master`` — parent branch
|
||||
* ``-C CHANGELEVEL`` — changelevel at which to make the branch
|
||||
* ``-v`` — request a version branch
|
||||
* ``-d "DESCRIPTION"`` — description of the branch
|
||||
* ``-d "DESCRIPTION"`` — description of the branch (see below)
|
||||
* ``-y`` — yes, really create the branch
|
||||
|
||||
The branch description will be published in the version index and
|
||||
should be a short summary of the improvements detailed in the release
|
||||
notes.
|
||||
|
||||
If omitted, the project and parent branch are deduced from the current
|
||||
directory, and the changelevel defaults to the most recent change on
|
||||
the parent branch. A typical invocation looks like this::
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue