Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [psa] various server software upgrades
Date: Mon, 7 Dec 2015 18:52:25 -0500	[thread overview]
Message-ID: <20151207235225.GG24430@vapier.lan> (raw)
In-Reply-To: <20151207195924.GH4258@free.fr>

On 07 Dec 2015 20:59, Yann E. MORIN wrote:
> On 2015-12-07 14:57 -0500, Mike Frysinger spake thusly:
> > On 07 Dec 2015 13:52, Mike Frysinger wrote:
> > > On 07 Dec 2015 09:00, Peter Korsgaard wrote:
> > > > FYI, there also seems to be an issue with the git.* certificates and
> > > > atleast python on the box, as I get this when pushing:
> > > 
> > > the certs shouldn't be causing issues with `git push` ...
> > > i'll take a look at that
> > 
> > was there a commit bot operating in #buildroot ?  i can't find references
> > to the client that actually connected to freenode.
> 
> Yes, we add a commit bot, but it disapeared a while ago.
> 
> I tried to follow the explanations to launmch it again, but it did not
> work (and I'm no longer sudoer, so I could not dedicate mor etime on it).
> 
> It would be nice if you could re-launch it, yes! ;-)

should be restored.  lemme know if you see any other issues.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151207/1b263203/attachment.asc>

  reply	other threads:[~2015-12-07 23:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  7:35 [Buildroot] [psa] various server software upgrades Mike Frysinger
2015-12-02  7:58 ` Lionel Orry
2015-12-02  8:43   ` Peter Korsgaard
2015-12-02  9:25 ` Nikolay Dimitrov
2015-12-02  9:28   ` Nikolay Dimitrov
2015-12-02 17:31   ` Mike Frysinger
2015-12-02 18:38     ` Nikolay Dimitrov
2015-12-06 21:42 ` Yann E. MORIN
2015-12-06 22:00   ` Peter Korsgaard
2015-12-07  1:55     ` Mike Frysinger
2015-12-07  6:34       ` Peter Korsgaard
2015-12-07 18:51         ` Mike Frysinger
2015-12-07 20:37           ` Peter Korsgaard
2015-12-07 21:55             ` Mike Frysinger
2015-12-07 22:16               ` Peter Korsgaard
2015-12-07 22:54                 ` Mike Frysinger
2015-12-07 23:02                   ` Yann E. MORIN
2015-12-07 23:22                     ` Mike Frysinger
2015-12-08  7:52                       ` Peter Korsgaard
2015-12-08 16:40                         ` Mike Frysinger
2015-12-08 16:43                           ` Peter Korsgaard
2015-12-08 17:27                             ` Mike Frysinger
2015-12-08  7:50                   ` Peter Korsgaard
2015-12-08  0:17                 ` Mike Frysinger
2015-12-08  7:55                   ` Peter Korsgaard
2015-12-08 16:38                     ` Mike Frysinger
2015-12-07  8:00       ` Peter Korsgaard
2015-12-07  8:23         ` Peter Korsgaard
2015-12-07 18:52         ` Mike Frysinger
2015-12-07 19:57           ` Mike Frysinger
2015-12-07 19:59             ` Yann E. MORIN
2015-12-07 23:52               ` Mike Frysinger [this message]
2015-12-07 20:42           ` Peter Korsgaard

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=20151207235225.GG24430@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=buildroot@busybox.net \
    /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