[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nPJHW_2B34d4jScTuvFA=Ux+EszvLN-p=wwPd5sFt54Q@mail.gmail.com>
Date: Sun, 12 Jan 2025 17:33:10 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Neal Gompa <neal@...pa.dev>
Cc: Miguel Ojeda <ojeda@...nel.org>, Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev, Sami Tolvanen <samitolvanen@...gle.com>,
Masahiro Yamada <masahiroy@...nel.org>, Luis Chamberlain <mcgrof@...nel.org>,
tech-board@...ups.linuxfoundation.org, Steven Rostedt <rostedt@...dmis.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>, Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH 3/3] docs: submitting-patches: clarify that signers may
use their discretion on tags
On Sun, Jan 12, 2025 at 4:47 PM Neal Gompa <neal@...pa.dev> wrote:
>
> A tag must not be dropped without the tag submitter's authorization.
Tags get routinely dropped, as the commit message explains. So we
cannot say "must not", sorry.
Even if that were not the case, tags are currently added/decided by
signers, not tag providers. This patch is trying to document how it
works today.
I understand it may feel bad to not have a tag applied, but it is
something normal in the current process. Tags are publicly archived
nevertheless, so e.g. one can still prove work to others.
I don't think misunderstandings about development processes mean
people is "rude": it may feel bad, but that does not mean others are
"rude" necessarily, unless they were rude in their manners or
something like that, which is not what is being discussed here.
Thanks for the quick review!
Cheers,
Miguel
Powered by blists - more mailing lists