From: Federico Mena Quintero <federico@gnome.org>
To: "Mark Wielaard" <mark@klomp.org>,
"Santiago Ruano Rincón" <santiago@debian.org>
Cc: bzip2-devel@sourceware.org,
Anibal Monsalve Salazar <anibal@debian.org>,
Anthony Fok <foka@debian.org>
Subject: Re: Releasing bzip2 1.0.7 and 1.1.0 ? Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <9fe6e535d2a9b4db4a0a3531285ffc31e8addc88.camel@gnome.org> (raw)
In-Reply-To: <b362ae8fc895d46a669a160257f27aa9d2f421ac.camel@klomp.org>
On Thu, 2019-06-27 at 20:00 +0200, Mark Wielaard wrote:
>
> I'll run the prepare-release.sh and release-update.sh scripts
> creating
> the 1.0.7 release and will then update bzip-htdocs.git to add a
> pointer
> to the homepage for the current development future 1.1.x development
> branch https://gitlab.com/federicomenaquintero/bzip2 for people who
> want a new build system and more fixes.
>
Thank you! Once you are done, I'll push a branch to the gitlab repo
with those changes. In the meantime I'll blog about your plans to keep
the 1.0.7 code there, and about 1.1.x being the version with the new
build systems.
Federico
next prev parent reply other threads:[~2019-06-27 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
2019-01-01 0:00 ` Santiago Ruano Rincón
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Releasing bzip2 1.0.7 and 1.1.0 ? Was: " Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero [this message]
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Some cherry-picks (Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.) Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
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=9fe6e535d2a9b4db4a0a3531285ffc31e8addc88.camel@gnome.org \
--to=federico@gnome.org \
--cc=anibal@debian.org \
--cc=bzip2-devel@sourceware.org \
--cc=foka@debian.org \
--cc=mark@klomp.org \
--cc=santiago@debian.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).