public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org,
	gentoo dev announce <gentoo-dev-announce@lists.gentoo.org>
Cc: council@gentoo.org
Subject: Re: Git workflow GLEP (Was: Re: [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC)
Date: Sat, 30 Sep 2017 19:32:12 +0200	[thread overview]
Message-ID: <1506792732.5672.0.camel@gentoo.org> (raw)
In-Reply-To: <d7da4951-e7df-86a0-21c8-44f9c84b6f6f@gentoo.org>

W dniu pią, 29.09.2017 o godzinie 14∶45 +0200, użytkownik Kristian
Fiskerstrand napisał:
> On 09/28/2017 10:17 PM, Michał Górny wrote:
> > > > >  If so (c) is there
> > > > > a benefit in using a full URI for Bug; or should this be reduced to only
> > > > > the number,
> > > > 
> > > > Only full URIs are acceptable. Numbers are ambiguous. The repository
> > > > and commits within it are mirrored to various sources, can be included
> > > > in external repositories and so on. We don't want to start closing
> > > > accidental bugs all over the place just because someone cherry-picked
> > > > a commit without escaping all references Gentoo developers left.
> > > > 
> > > 
> > > Which could also be seen as an argument for Gentoo-Bug: XXXXXX
> > > 
> > 
> > And then Gentoo-Closes, Debian-Closes, Fancybuntu-Closes, My-Fun-
> > Upstream-Tracker-Bug...
> 
> Not really, Closes is already used for multiple providers of
> infrastructure such as Bitbucket and GitHub, so here URI is anyways
> needed and isn't specific to Gentoo. Debian bug wouldn't be closed by us
> to begin with, but it'd fit into a generic Reference: tag if we pulled a
> patch from it or it discusses it somehow. Ditto for upstream, that goes
> in Reference as well
> 

How is this an argument for introducing a completely incompatible
and inconsistent concept for the other of the pair?

-- 
Best regards,
Michał Górny



  reply	other threads:[~2017-09-30 17:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 15:08 [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC Andreas K. Huettel
2017-09-26 18:58 ` Michał Górny
2017-09-27 19:24   ` Michał Górny
2017-09-28  9:06     ` Git workflow GLEP (Was: Re: [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC) Kristian Fiskerstrand
2017-09-28 19:46       ` Michał Górny
2017-09-28 19:56         ` Kristian Fiskerstrand
2017-09-28 20:17           ` Michał Górny
2017-09-29 12:45             ` Kristian Fiskerstrand
2017-09-30 17:32               ` Michał Górny [this message]
2017-09-30 17:36                 ` Kristian Fiskerstrand
2017-09-30 18:48                   ` Michał Górny
2017-10-01 20:37                     ` Andreas K. Huettel
2017-10-02 12:01                       ` Kristian Fiskerstrand
2017-09-29 13:10         ` Kristian Fiskerstrand
2017-10-01 20:41     ` [gentoo-project] Call for agenda items, council meeting 8/October/2017 18:00 UTC Andreas K. Huettel
2017-10-01 21:04       ` Michał Górny
2017-10-02 19:25 ` [gentoo-project] Re: [gentoo-dev-announce] " Ulrich Mueller
2017-10-02 19:33   ` Kristian Fiskerstrand
2017-10-02 19:58     ` Rich Freeman
2017-10-02 20:01       ` Kristian Fiskerstrand
2017-10-02 20:05         ` Michał Górny
2017-10-02 20:15           ` Rich Freeman
2017-10-03 11:05         ` Ulrich Mueller
2017-10-03 11:10           ` Kristian Fiskerstrand
2017-10-03 18:13             ` Michał Górny
2017-10-03 12:39           ` Rich Freeman
2017-10-03 16:57             ` Ulrich Mueller

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=1506792732.5672.0.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /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