On czw, 2017-07-27 at 15:54 +0200, Kristian Fiskerstrand wrote:
> On 07/27/2017 03:52 PM, Michał Górny wrote:
> > On śro, 2017-07-26 at 19:17 +0200, Kristian Fiskerstrand wrote:
> > > On 07/25/2017 10:05 AM, Michał Górny wrote:
> > > > ** <kbd>Fixes: <nowiki>https://bugs.gentoo.org/NNNNNN</nowiki></kbd>;;; 
> > > > —
> > > > to indicate a fixed bug,
> > > 
> > > At this point fixes is overloading
> > > > ** <kbd>Fixes: commit-id (commit message)</kbd> — to indicate fixing a
> > > > previous commit
> > > 
> > > This use should be forbidden.
> > 
> > ...because? But sure, you don't like it, let's remove it. Not that
> > anyone will actually prefer the things from the GLEP over anything else.
> > 
> 
> Because it overloads the tag for multiple meanings and as such should be
> different tags, we already have a tag that specifies the bug (namely
> Bug, presuming we use Reference: for URL specification of relevant
> upstream information or other discussions)
> 
> > > > ** <kbd>Bug: <nowiki>https://bugs.gentoo.org/NNNNNN</nowiki></kbd>;;; — 
> > > > to
> > > > reference a bug,
> > > 
> > > See other comments in thread wrt Gentoo-Bug.
> > > 
> > > > ** <kbd>Closes: <nowiki>https://github.com/gentoo/gentoo/pull/NNNN</nowi
> > > > ki></kbd>; — to automatically close a GitHub pull request,
> > > 
> > > Is this a generic tag for any pull request of any platform?
> > 
> > No. As I've told multiple times already, there are *no* generic tags. It
> > just happens to be used by some random platforms. Some others use e.g.
> > 'Fixes' which you forbade.
> > 
> 
> Isn't that the point of having a GLEP to begin with? Trying to
> standardize the use of e.g the tags so that it has a consistent meaning
> and can be useful?
> 

Tags are mentioned merely for convenience, and as examples. If you want
to request GitHub support to add support for special Gentoo tags you've
just invented, be my guest. But don't bother forwarding their reply to
me because I know their answer.

-- 
Best regards,
Michał Górny

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to