kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-11-19 16:20:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: Fix CHANGES entries to have .txt suffix and update READMEs

Browse Source 
Although the wiki page for the new CHANGES and UPGRADE scheme
states that the files must have the ".txt" suffix, the READMEs
didn't.

Change-Id: I490306aa2cc24d6f014738e9ebbc78592efe0f05
This commit is contained in:
George Joseph
2020-02-07 12:44:50 -07:00
parent 443230f5d5
commit 7416703f04
4 changed files with 8 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/CHANGES-staging/README.md
View File

@@ -9,10 +9,10 @@ it probably should. If there are multiple items that need documenting, you can
add multiple files, each with their own description. If the message is going to
be the same for each subject, then you can add multiple subject headers to one
file. The "Subject: xxx" line is case sensitive! For example, if you are making
a change to PJSIP, then you might add the file "res_pjsip_my_cool_feature" to
this directory, with a short description of what it does. If you are adding
multiple entries, they should be done in the same commit to avoid merge
conflicts. Here's an example:
a change to PJSIP, then you might add the file "res_pjsip_my_cool_feature.txt" to
this directory, with a short description of what it does. The files must have
the ".txt" suffix. If you are adding multiple entries, they should be done in
the same commit to avoid merge conflicts. Here's an example:
> Subject: res_pjsip
> Subject: Core

0
doc/CHANGES-staging/hide_messaging_ami_events → doc/CHANGES-staging/hide_messaging_ami_events.txt
View File

7
doc/CHANGES-staging/res_fax_negotiate_both
View File

@@ -1,7 +0,0 @@
Subject: res_fax
Added configuration option "negotiate_both". This option is only used
when a gateway is enabled, and a v21 preamble is detected. If this option
is enabled, once a preamble is detected Asterisk will initiate negotiation
requests to both T.38 enabled endpoint versus waiting, and forwarding a
request from an initiating endpoint. Defaults to disabled.

7
doc/UPGRADE-staging/README.md
View File

@@ -9,9 +9,10 @@ are multiple items that need documenting, you can add multiple files, each with
their own description. If the message is going to be the same for each subject,
then you can add multiple subject headers to one file. The "Subject: xxx" line
is case sensitive! For example, if you are making a change to PJSIP, then you
might add the file "res_pjsip_my_cool_feature" to this directory, with a short
description of what it does. If you are adding multiple entries, they should be
done in the same commit to avoid merge conflicts. Here's an example:
might add the file "res_pjsip_my_cool_feature.txt" to this directory, with a
short description of what it does. The files must have the ".txt" suffix.
If you are adding multiple entries, they should be done in the same commit
to avoid merge conflicts. Here's an example:
> Subject: res_pjsip
> Subject: Core