All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,  git@vger.kernel.org
Subject: Re: Ejecting things more aggressively out of 'seen'?
Date: Fri, 06 Nov 2026 12:38:57 -0800	[thread overview]
Message-ID: <xmqqqzgxg0f2.fsf@gitster.g> (raw)
In-Reply-To: <48a6c039-75b6-4fa4-a18e-ea3240037be9@gmail.com> (Phillip Wood's message of "Mon, 2 Nov 2026 16:34:23 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

> Perhaps making it clear that when a topic is ejected it can be re-added 
> if there is renewed interest in it would lessen any worry about 
> demotivating contributors?

Yes, that is a good suggestion.

Mentioning this possibility when a topic is ejected from 'seen'
should help soften the impact and clarify that ejection is not a
permanent rejection, just a reflection of current review.

I'll try this as the heading for the discarded section.

    [Discarded]

    Many of these topics were picked up prematurely but did not prove
    ready for inclusion, and will be removed.  They can be resubmit if
    they gained enough interest and showed good fit to the system in the
    future, unless noted otherwise.

  reply	other threads:[~2026-11-06 20:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  3:09 What's cooking in git.git (Jul 2026, #12) Junio C Hamano
2026-07-29 13:24 ` Phillip Wood
2026-07-29 14:18   ` Junio C Hamano
2026-07-29 15:20     ` Phillip Wood
2026-07-29 17:48       ` Junio C Hamano
2026-08-05 13:10         ` Phillip Wood
2026-08-05 17:03           ` Junio C Hamano
2026-11-02  7:31           ` Ejecting things more aggressively out of 'seen'? Junio C Hamano
2026-11-02  9:59             ` Patrick Steinhardt
2026-11-02 16:17               ` Junio C Hamano
2026-11-02 16:34                 ` Phillip Wood
2026-11-06 20:38                   ` Junio C Hamano [this message]
2026-11-03  7:30                 ` Patrick Steinhardt
2026-11-03 16:04                   ` Junio C Hamano
2026-11-03 19:29                   ` Junio C Hamano
2026-07-31  6:20     ` What's cooking in git.git (Jul 2026, #12) Matt Hunter
2026-07-31 15:36       ` Junio C Hamano
2026-07-30  6:11   ` Harald Nordgren
2026-07-31  7:02     ` Matt Hunter
2026-08-03  9:05       ` Phillip Wood
2026-08-03 16:02         ` Junio C Hamano
2026-08-04 13:19           ` Phillip Wood
2026-08-03  9:11     ` Phillip Wood
2026-07-29 15:14 ` Phillip Wood
2026-07-29 15:52   ` Junio C Hamano

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=xmqqqzgxg0f2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@gmail.com \
    --cc=ps@pks.im \
    /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.