control: tag -1 +pending


On Tue 07 Aug 2018 at 09:26am +0200, Clément Hermann wrote:

> IMO, s/maximally// would definitely fix the most pressing matter here,
> that is, the fact that we have incompatible statements. I would
> definitely be able to declare the go packages I maintain compliant, for
> instance.
> However, regarding the rest of the discussion on this bug, I agree more
> guidance to the maintainer as to what is expected would be nice. But
> that is a separate issue, I think.
> How about resolving this one with this simple fix and opening a new one
> to discuss making this paragraph better ?

On Tue 07 Aug 2018 at 11:10am -0700, Jonathan Nieder wrote:

> I don't believe s/maximally// changes the normative content --- it just
> more clearly expresses what it already is saying.  So I think a policy
> editor can make that change without waiting for seconds.

Thank you both.  Applied in git.

With regard to offering package maintainers more guidance as to how
verbose builds should be, I'll leave it up to Jonathan to either clone
this bug, or file a new one.

(I'm not sure whether Jonathan feels it is possible to summarise the
current discussion as the first message to a new bug, or whether things
are still sufficiently unclear that all the context needs to be

Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to