Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Hi Junio, > > On Fri, 2 Sep 2022, Junio C Hamano wrote: > >> "Julia Ramer via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: >> >> > diff --git a/Documentation/howto/coordinate-embargoed-releases.txt b/Documentation/howto/coordinate-embargoed-releases.txt >> > index 601aae88e9a..43400fd6025 100644 >> > --- a/Documentation/howto/coordinate-embargoed-releases.txt >> > +++ b/Documentation/howto/coordinate-embargoed-releases.txt >> > @@ -1,6 +1,121 @@ >> > Content-type: text/asciidoc >> > -Abstract: When a critical vulnerability is discovered and fixed, we follow this >> > - script to coordinate a public release. >> > +Abstract: When a vulnerability is reported, we follow these guidelines to >> > + assess the vulnerability, create and review a fix, and coordinate embargoed >> > + security releases. >> > + >> > +The `git-security` mailing list >> > +=============================== >> >> Dissapointingly, addition of these two new "=====" underlined >> sections breaks the documentation build, which broke mi build >> locally as well as GitHub CI [*1*] >> >> * https://github.com/git/git/runs/8162258928?check_suite_focus=true#step:4:658 >> >> Fix should hopefully be trivial, keep the original title line >> >> How we coordinate embargoed releases >> ==================================== >> >> intact, and make these two new sections underlined with "-----", >> demoting their subsections one level down accordingly. > > Here is a fixup, could you please apply this to the > `jr/embargoed-releases-doc` branch? Thanks but no thanks. The contents change is needed so I will wait for an updated patch from the author.
