On Wed, Nov 09, 2016 at 12:46:48PM +0100, Pierre-Yves Chibon wrote:
> On Tue, Nov 08, 2016 at 08:25:45PM -0500, Ralph Bean wrote:
> > On Tue, Nov 08, 2016 at 04:04:38PM +0100, Pierre-Yves Chibon wrote:
> > > On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> > > > This is likely also
On Tue, Nov 08, 2016 at 08:25:45PM -0500, Ralph Bean wrote:
> On Tue, Nov 08, 2016 at 04:04:38PM +0100, Pierre-Yves Chibon wrote:
> > On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> > > This is likely also https://pagure.io/fedora-infrastructure/issue/4022
> > > Perhaps I should
On Tue, Nov 08, 2016 at 04:04:38PM +0100, Pierre-Yves Chibon wrote:
> On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> > This is likely also https://pagure.io/fedora-infrastructure/issue/4022
> > Perhaps I should close that one UPSTREAM?
> > (I have no idea if it still needs fixing)
On Tue, 8 Nov 2016 16:04:38 +0100
Pierre-Yves Chibon wrote:
> On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> > This is likely also
> > https://pagure.io/fedora-infrastructure/issue/4022 Perhaps I should
> > close that one UPSTREAM? (I have no idea if it still
On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote:
> This is likely also https://pagure.io/fedora-infrastructure/issue/4022
> Perhaps I should close that one UPSTREAM?
> (I have no idea if it still needs fixing)
Nah that's bug in our git hook that is in ansible.
There are two ways to
On Wed, 2 Nov 2016 16:24:40 +0100
Aurelien Bompard <abomp...@fedoraproject.org> wrote:
> Hey folks,
>
> I'd like to do some triage of the fedmsg issues currently open on
> Github, then discuss with you what we should prioritize and decide on
> a roadmap. Triage, first. I
Hey folks,
I'd like to do some triage of the fedmsg issues currently open on Github,
then discuss with you what we should prioritize and decide on a roadmap.
Triage, first. I haven't had a chance to get to know fedmsg inimately
enough so I hope you'll correct me. Here is the list of open issues