public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Modernize gettext infrastructure
Date: Wed, 16 Dec 2020 16:10:44 +0100	[thread overview]
Message-ID: <96b41a99de812dba0edf9a72e5e05444dab32c71.camel@klomp.org> (raw)
In-Reply-To: <20201216145945.GB30159@altlinux.org>

Hi Dmitry,

On Wed, 2020-12-16 at 17:59 +0300, Dmitry V. Levin wrote:
> > I don't know if all the
> > buildbot workers have it installed, so when you do check it in please
> > keep an eye on 
> > https://builder.wildebeest.org/buildbot/#/builders?tags=elfutils
> 
> Is there a way to find it out beforehand?

No, sorry, not at the moment. You'll just have to push and see.

I'll see if I can add try-server support to the buildbot this end-of-
year vacation, but no promises.

If there are issues on any of the buildbots that aren't clear then
shell access can be arranged, but different people maintain different
machines.

Cheers,

Mark

      reply	other threads:[~2020-12-16 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 23:40 Dmitry V. Levin
2020-12-15 23:46 ` Q: splitting the top level .gitignore file Dmitry V. Levin
2020-12-16 13:44   ` Mark Wielaard
2020-12-20 12:11     ` [PATCH 1/2] Split " Dmitry V. Levin
2020-12-20 15:28       ` Mark Wielaard
2020-12-20 15:37         ` Dmitry V. Levin
2020-12-20 15:59           ` Dmitry V. Levin
2020-12-20 16:09             ` Mark Wielaard
2020-12-20 12:11     ` [PATCH 2/2] Update .gitignore files Dmitry V. Levin
2020-12-16 14:05 ` [PATCH] Modernize gettext infrastructure Mark Wielaard
2020-12-16 14:59   ` Dmitry V. Levin
2020-12-16 15:10     ` Mark Wielaard [this message]

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=96b41a99de812dba0edf9a72e5e05444dab32c71.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ldv@altlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).