public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Simon Chopin <simon.chopin@canonical.com>, buildbot@sourceware.org
Subject: Re: [PATCH] Enable glibc builds on stable release branches
Date: Mon, 17 Apr 2023 14:55:41 +0200	[thread overview]
Message-ID: <baeaf8e303921448badd7c1d90b892391728028f.camel@klomp.org> (raw)
In-Reply-To: <CAOOWow01De4uFbKW9Db-OXXk-YW=EkFZARL0w4z-kK1eeT0s7A@mail.gmail.com>

Hi Simon,

On Mon, 2023-04-17 at 13:06 +0200, Simon Chopin wrote:
> The glibc 2.37 release announcement contains an exlicit call for
> distributions to track the stable release branches. In light of this, I
> think it makes sense for those branches to have CI coverage similar to
> the master branch.

Makes sense and looks good. Pushed.

Thanks,

Mark

P.S. It did have some odd whitespace issues, easily resolved, but you
might want to look at why your mailer wraps lines.

      reply	other threads:[~2023-04-17 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 11:06 Simon Chopin
2023-04-17 12:55 ` 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=baeaf8e303921448badd7c1d90b892391728028f.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=simon.chopin@canonical.com \
    /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).