mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-13 00:04:53 +00:00
doc: Fix CHANGES entries to have .txt suffix and update READMEs
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
(cherry picked from commit 7416703f04
)
This commit is contained in:
@@ -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
|
||||
|
Reference in New Issue
Block a user