public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-project@lists.gentoo.org,
	"Michał Górny" <mgorny@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: Fri, 29 Sep 2017 14:45:43 +0200	[thread overview]
Message-ID: <d7da4951-e7df-86a0-21c8-44f9c84b6f6f@gentoo.org> (raw)
In-Reply-To: <1506629873.15843.7.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1233 bytes --]

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

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-09-29 12:45 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 [this message]
2017-09-30 17:32               ` Michał Górny
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=d7da4951-e7df-86a0-21c8-44f9c84b6f6f@gentoo.org \
    --to=k_f@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@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