mirrors/zsh
1
0
Fork 0
mirror of git://git.code.sf.net/p/zsh/code synced 2025-01-01 05:16:05 +01:00
Code Releases Activity

47308: zsh-development-guide: Document the new X-Seq autoreply bot.

Browse source
This commit is contained in:
Daniel Shahaf 2020-08-09 02:42:25 +00:00
parent 5448e1611d
commit 1f8adb4785
2 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
2020-08-10 Daniel Shahaf <d.s@daniel.shahaf.name>
* 47308: Etc/zsh-development-guide: Document the new X-Seq
autoreply bot.
2020-08-09 Daniel Shahaf <d.s@daniel.shahaf.name> 2020-08-09 Daniel Shahaf <d.s@daniel.shahaf.name>
* 47303: Functions/VCS_Info/Backends/VCS_INFO_get_data_hg, * 47303: Functions/VCS_Info/Backends/VCS_INFO_get_data_hg,

8
Etc/zsh-development-guide
View file

@ -66,6 +66,14 @@ avoided further changes to our workflow.
the mailing list sequence number. This number is generated by the list the mailing list sequence number. This number is generated by the list
server and inserted as an X-Seq: header field in the e-mail. server and inserted as an X-Seq: header field in the e-mail.
Your email client may be able to be configured to show the X-Seq:
header by default, and probably has a way to view the raw full headers
of an email. The X-Seq header is also shown on the
https://www.zsh.org/mla/ email archives. We can also, upon request,
set up an email-based bot that, whenever you post a patch to the
mailing list, will send you an offlist reply with the X-Seq number of
your patch.
* An entry in the ChangeLog file should be added manually before pushing * An entry in the ChangeLog file should be added manually before pushing
a commit to the master repository. Don't create a separate change for a commit to the master repository. Don't create a separate change for
this: amend the existing commit in your local repository. this: amend the existing commit in your local repository.