Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: propose community voting process
Date: Fri, 30 Oct 2026 10:44:38 -0700	[thread overview]
Message-ID: <xmqqfqxnw0ah.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZmyADCU8VdVDrvR-OuDKybSnT2pMOKbrofRBg6YdpxZ0A@mail.gmail.com> (Emily Shaffer's message of "Fri, 30 Oct 2026 10:15:57 -0700")

Emily Shaffer <nasamuffin@google.com> writes:

> Changes I will make:
> * Modify the subject line so that it makes sense after merging, from
> "Propose..." to "Specify..." a voting policy.
> * Make explicit the requirement for secret votes.

OK.

> * Specify that we will vote on _only_ the most recent version of a
> proposal (not an earlier one), and that votes should refer to the
> commit ID of a patch in Junio's tree, not a particular subject line on
> the mailing list.

Please make them refer to the Message-ID instead.  These commit
object names will change if I have to requeue the same message for
any reason.

Thanks.

  reply	other threads:[~2026-10-30 17:44 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 18:05 Notes from the Git Contributor's Summit, 2026 Taylor Blau
2026-10-06 18:06 ` [NOTES 01/07] Security mailing list and security process Taylor Blau
2026-10-06 18:06 ` [NOTES 02/07] Git 3.0 Taylor Blau
2026-10-06 18:06 ` [NOTES 03/07] Documentation Taylor Blau
2026-10-07  4:49   ` Todd Zullinger
2026-10-07 17:38     ` Junio C Hamano
2026-10-06 18:06 ` [NOTES 04/07] Outreachy sponsorship Taylor Blau
2026-10-06 18:06 ` [NOTES 05/07] What can we do next with pluggable ODB? Taylor Blau
2026-10-06 18:06 ` [NOTES 06/07] AI contribution policy Taylor Blau
2026-10-21 20:03   ` [PATCH] Documentation: propose community voting process Emily Shaffer
2026-10-21 20:05     ` Emily Shaffer
2026-10-22 10:01       ` Phillip Wood
2026-10-23  4:48         ` Junio C Hamano
2026-10-23 13:49           ` Phillip Wood
2026-10-23 14:18             ` Kristoffer Haugsbakk
2026-10-23 16:26               ` Junio C Hamano
2026-10-23 18:09                 ` Kristoffer Haugsbakk
2026-10-23 22:08                   ` Junio C Hamano
2026-10-23 14:31           ` Kristoffer Haugsbakk
2026-10-24 11:18           ` Tuomas Ahola
2026-10-24 13:03             ` Weijie Yuan
2026-10-30  6:35               ` Toon Claes
2026-10-30  7:18                 ` Weijie Yuan
2026-10-24 14:56             ` Junio C Hamano
2026-10-24 15:06               ` Weijie Yuan
2026-10-26  1:17             ` Jeff King
2026-10-26  3:50               ` Junio C Hamano
2026-10-26  7:57               ` Patrick Steinhardt
2026-10-26  9:23                 ` Tuomas Ahola
2026-10-30 16:50                 ` Emily Shaffer
2026-10-30 17:18                   ` Junio C Hamano
2026-10-30 18:00                   ` Jeff King
2026-10-26 10:41               ` Phillip Wood
2026-10-22 22:59       ` brian m. carlson
2026-10-21 21:22     ` Junio C Hamano
2026-10-21 22:06     ` Junio C Hamano
2026-10-22 15:35       ` Justin Tobler
2026-10-23  4:56         ` Junio C Hamano
2026-10-30 16:30       ` Emily Shaffer
2026-10-22  7:29     ` Kristoffer Haugsbakk
2026-10-22 12:44       ` Patrick Steinhardt
2026-10-22 22:51       ` brian m. carlson
2026-10-22 23:17         ` Junio C Hamano
2026-10-30 16:53           ` Emily Shaffer
2026-10-23  4:51         ` Kristoffer Haugsbakk
2026-10-30 17:15     ` Emily Shaffer
2026-10-30 17:44       ` Junio C Hamano [this message]
2026-10-30 21:03       ` Jonathan Corbet
2026-10-06 18:06 ` [NOTES 07/07] Protocol v2 for pushes Taylor Blau

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=xmqqfqxnw0ah.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox