a294443fa1
With the recent turnover on the git-security list, questions came up how things are usually run. Rather than answering questions individually, extend Git's existing documentation about security vulnerabilities to describe the git-security mailing list, how things are run on that list, and what to expect throughout the process from the time a security bug is reported all the way to the time when a fix is released. Helped-by: Junio C Hamano <gitster@pobox.com> Helped-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Julia Ramer <gitprplr@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> |
||
|---|---|---|
| .. | ||
| coordinate-embargoed-releases.txt | ||
| keep-canonical-history-correct.txt | ||
| maintain-git.txt | ||
| new-command.txt | ||
| rebase-from-internal-branch.txt | ||
| rebuild-from-update-hook.txt | ||
| recover-corrupted-blob-object.txt | ||
| recover-corrupted-object-harder.txt | ||
| revert-a-faulty-merge.txt | ||
| revert-branch-rebase.txt | ||
| separating-topic-branches.txt | ||
| setup-git-server-over-http.txt | ||
| update-hook-example.txt | ||
| use-git-daemon.txt | ||
| using-merge-subtree.txt | ||
| using-signed-tag-in-pull-request.txt | ||