09420b7648
Whenever we fix critical vulnerabilities, we follow some sort of protocol (e.g. setting a coordinated release date, keeping the fix under embargo until that time, coordinating with packagers and/or hosting sites, etc). Similar in spirit to `Documentation/howto/maintain-git.txt`, let's formalize the details in a document. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> 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 | ||