1
0
Fork 0
mirror of https://github.com/git/git.git synced 2024-05-25 07:46:15 +02:00
git/Documentation/howto
Johannes Schindelin 09420b7648 Document how we do embargoed releases
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>
2021-03-27 15:13:12 -07:00
..
coordinate-embargoed-releases.txt Document how we do embargoed releases 2021-03-27 15:13:12 -07:00
keep-canonical-history-correct.txt
maintain-git.txt Merge branch 'js/pu-to-seen' 2020-07-06 22:09:16 -07:00
new-command.txt
rebase-from-internal-branch.txt docs: adjust the technical overview for the rename `pu` -> `seen` 2020-06-25 09:18:55 -07:00
rebuild-from-update-hook.txt
recover-corrupted-blob-object.txt
recover-corrupted-object-harder.txt
revert-a-faulty-merge.txt
revert-branch-rebase.txt docs: adjust the technical overview for the rename `pu` -> `seen` 2020-06-25 09:18:55 -07:00
separating-topic-branches.txt Documentation: fix a bunch of typos, both old and new 2019-11-07 13:42:00 +09:00
setup-git-server-over-http.txt doc: format pathnames and URLs as monospace. 2019-03-13 11:14:22 +09:00
update-hook-example.txt docs: adjust the technical overview for the rename `pu` -> `seen` 2020-06-25 09:18:55 -07:00
use-git-daemon.txt
using-merge-subtree.txt howto/using-merge-subtree: mention --allow-unrelated-histories 2018-10-25 14:45:15 +09:00
using-signed-tag-in-pull-request.txt