Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 560B8AF2.9020206@BlueTreble.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/29/15 12:46 PM, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
>> On 2015-09-29 13:40:28 -0400, Tom Lane wrote:
>>> I think you missed my point: gitlab would then believe it's in charge of,
>>> eg, granting write access to that repo.  We could perhaps whack it over
>>> the head till it only does what we want and not ten other things, but
>>> we'd be swimming upstream.
>
>> We today already have a github mirror, where exactly the same thing
>> exists, no?
>
> Sure, there's a mirror out there somewhere.  It has nothing to do with
> our core development processes.

There are APIs as well, so it could be driven that way. I suspect it's 
unnecessary though.

BTW, the docs are at http://doc.gitlab.com/ce/.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: No Issue Tracker - Say it Ain't So!
Next
From:
Date:
Subject: Standby server crashes in master and REL9_5_STABLE branches