All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Julia Ramer via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, git-security@googlegroups.com,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Julia Ramer <prplr@github.com>,
	Keanen Wold <keanenwold@github.com>,
	Veronica Giaudrone <veronica.Giaudrone@microsoft.com>,
	Bri Brothers <brbrot@microsoft.com>,
	Taylor Blau <me@ttaylorr.com>, Julia Ramer <gitprplr@gmail.com>
Subject: Re: [PATCH v4] embargoed releases: also describe the git-security list and the process
Date: Mon, 24 Oct 2022 16:08:47 -0700	[thread overview]
Message-ID: <xmqqa65krf9c.fsf@gitster.g> (raw)
In-Reply-To: <pull.1345.v4.git.1666649239302.gitgitgadget@gmail.com> (Julia Ramer via GitGitGadget's message of "Mon, 24 Oct 2022 22:07:19 +0000")

"Julia Ramer via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: Julia Ramer <gitprplr@gmail.com>
>
> 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>
> ---
>     embargoed releases: also describe the git-security list and the process
>     
>     Changes since v3:
>     
>      * minor formatting corrections
>      * clarified the language based on v3 feedback

Thanks, this version I am happy with.

      reply	other threads:[~2022-10-25  0:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 22:39 [PATCH] embargoed releases: also describe the git-security list and the process Julia Ramer via GitGitGadget
2022-09-02 17:24 ` Junio C Hamano
2022-09-27 22:56   ` Julia Ramer
2022-09-28 17:12     ` Junio C Hamano
2022-10-18 20:43       ` Julia Ramer
2022-10-19 15:47         ` Junio C Hamano
2022-09-02 18:59 ` Junio C Hamano
2022-09-03  9:29   ` Johannes Schindelin
2022-09-05 20:28     ` Junio C Hamano
2022-10-19  1:16 ` [PATCH v2] " Julia Ramer via GitGitGadget
2022-10-19 18:53   ` Junio C Hamano
2022-10-19 21:22     ` Taylor Blau
2022-10-19 22:01     ` Junio C Hamano
2022-10-19 21:15   ` Taylor Blau
2022-10-19 21:50     ` Junio C Hamano
2022-10-20 17:06     ` Taylor Blau
2022-10-21  7:41   ` [PATCH v3] " Julia Ramer via GitGitGadget
2022-10-21 16:42     ` Junio C Hamano
2022-10-24 20:18       ` Julia Ramer
2022-10-24 22:56         ` Junio C Hamano
2022-10-22  0:11     ` Taylor Blau
2022-10-24 20:19       ` Julia Ramer
2022-10-24 22:07     ` [PATCH v4] " Julia Ramer via GitGitGadget
2022-10-24 23:08       ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqa65krf9c.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=brbrot@microsoft.com \
    --cc=git-security@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitprplr@gmail.com \
    --cc=keanenwold@github.com \
    --cc=me@ttaylorr.com \
    --cc=prplr@github.com \
    --cc=veronica.Giaudrone@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.