From: Dagobert Michelsen <dam@opencsw.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: release process analysis
Date: Tue, 29 Sep 2020 09:00:47 +0200 [thread overview]
Message-ID: <80B1E2F7-4E98-4CB5-9469-C2E14684DA0E@opencsw.org> (raw)
In-Reply-To: <1747048.bxoIWskaFC@omega>
Hi Bruno,
Am 29.09.2020 um 04:28 schrieb Bruno Haible <bruno@clisp.org>:
> - we don't have continuous integration on Solaris,
This is not correct: there is continous integration on Solaris
for quite some time now and status changes are reported
automatically to grep-devel@gnu.org as well:
https://buildfarm.opencsw.org/buildbot/waterfall?category=ggrep
If there are any changes needed please let me know.
Best regards
— Dago
--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896
next prev parent reply other threads:[~2020-09-29 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 2:02 grep-3.5 fails to build on Solaris when libsigsegv is installed Bruno Haible
2020-09-29 2:28 ` release process analysis Bruno Haible
2020-09-29 7:00 ` Dagobert Michelsen [this message]
2020-09-29 20:56 ` Paul Eggert
2020-09-29 21:10 ` Dagobert Michelsen
2020-09-29 20:56 ` Jeffrey Walton
2020-09-29 22:32 ` Bruno Haible
2020-10-04 23:26 ` grep-3.5 fails to build on Solaris when libsigsegv is installed Paul Eggert
2020-10-04 23:40 ` AS_IF Bruno Haible
2020-10-05 1:50 ` AS_IF Paul Eggert
2020-10-06 21:56 ` AS_IF Bruno Haible
2020-10-07 0:52 ` AS_IF Zack Weinberg
2020-10-12 7:01 ` AS_IF Paul Eggert
2020-10-12 12:57 ` AS_IF Zack Weinberg
2020-10-05 8:06 ` grep-3.5 fails to build on Solaris when libsigsegv is installed Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80B1E2F7-4E98-4CB5-9469-C2E14684DA0E@opencsw.org \
--to=dam@opencsw.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).