X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=W5kdO0YMr1B9YaQ99yC2z2i4Th6uVhbAJQ63FMDfiBE=;
        b=mcmulCGDulrwgeYl23hXGFAoYENbE+JO5jcpvZYykFM621xG7pvhXdVU5gXxb9fV7u
         KeVdxK/nzOJ8kebSan1BBiXkvDPkcyuMS1kM7HIrzQbTnXjB8MOOHvJSxch5mqhggLah
         R63nmH6A5amZ46pddLJsGzsM1qfWyLFijHrTcmRINFc7Jzz+5y5F7CSo0V+iNzBgFJ3d
         Bx37R4abUJh8xhB1jkusWGliasbFN3X/j0INiMfpJUsZMD446y4wpIAA5XFBH6k18wPm
         8MrjjFE94VCczKA2QMWrE9MVgZ819B5FUYRfudbbp7Xfh0Fvv6QLjEmnGYC6kA7qvpoT
         bGrg==
MIME-Version: 1.0
X-Received: by 10.194.178.196 with SMTP id da4mr11489820wjc.41.1445422557446;
 Wed, 21 Oct 2015 03:15:57 -0700 (PDT)
In-Reply-To: <201510202136.t9KLaTdD025730@envy.delorie.com>
References: <CABuVar+HkYipLNEXbTFoegy66QqtJGSf7kdzDAOCvrRBKjTj9w AT mail DOT gmail DOT com>
	<201510202136 DOT t9KLaTdD025730 AT envy DOT delorie DOT com>
Date: Wed, 21 Oct 2015 13:15:57 +0300
Message-ID: <CAMvDHVBLV8B3jXBNCS=Qw5TtRxAj4rzkaXQnvcnsFkTftOJ3wg@mail.gmail.com>
Subject: Re: [geda-user] Something strange with gEDA git repositories
From: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 10/21/15, DJ Delorie <dj AT delorie DOT com> wrote:
>
> We disabled the commit robot because it kept breaking, but apparently
> only for the pcb repo.  I assume you're using a different repo?
> Should we disable the commit robot globally until it can be fixed?
> (unless someone wants to fix the robot?)
>

Not only for pcb. It behaves the same way with geda-gaf (and I
think with other geda repos).

If we disable it, nobody could recall that it needs to be fixed :)

I wanted to fix it, though realized I hardly find time for this
in the near future. IIUC, there is some info on how all that works
at [1] (too much reading for me yet :)).

[1] https://help.launchpad.net/API/SigningRequests