From: Guilhem Moulin <guilhem@fripost.org>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
Date: Fri, 25 Jan 2019 16:05:30 +0100 [thread overview]
Message-ID: <20190125150529.GA5585@fripost.org> (raw)
In-Reply-To: <71db2159-bb20-c9a5-19bc-c597b2a33788@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Fri, 25 Jan 2019 at 15:31:38 +0100, Milan Broz wrote:
> In short, this is the plan and major changes (I'll write more details later)
>
> - 2.1 should be released 5.2.2019
>
> (Definitely not later, some slight change that it happens earlier.
> I am traveling days before it, and we need some time for translators.
> But git will be almost ready for 2.1 next week.)
>
> - no soname bump, just compatible version increase (only added symbols)
> […]
> If you rely on some stable release earlier, let me know, please.
Excellent! So if we upload to sid later that day that gives us a full 5
weeks transition period for Buster. Given the significant list of major
changes we'd prefer not to upload at the very last minute, but 5 weeks
is plenty: as far as Debian is concerned there is no need to rush the
upstream release.
Thanks for the update!
--
Guilhem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-25 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 8:16 [dm-crypt] Debian installer formatting LUKS2 devices by default? Guilhem Moulin
2018-07-30 10:51 ` Milan Broz
2018-07-30 20:47 ` Guilhem Moulin
2018-07-31 6:00 ` Michael Kjörling
2018-07-31 7:53 ` Guilhem Moulin
2018-11-23 9:21 ` Milan Broz
2018-11-23 18:26 ` Guilhem Moulin
2018-11-23 18:46 ` Milan Broz
2019-01-25 13:54 ` Guilhem Moulin
2019-01-25 14:31 ` Milan Broz
2019-01-25 15:05 ` Guilhem Moulin [this message]
2019-02-05 15:29 ` Milan Broz
2018-07-31 8:56 ` Milan Broz
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=20190125150529.GA5585@fripost.org \
--to=guilhem@fripost.org \
--cc=dm-crypt@saout.de \
--cc=gmazyland@gmail.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