From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: 2.02~beta3 release
Date: Sun, 28 Feb 2016 19:44:03 +0300 [thread overview]
Message-ID: <56D323D3.7040909@gmail.com> (raw)
In-Reply-To: <56D32316.5040806@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
28.02.2016 19:40, Andrei Borzenkov пишет:
> You forgot to tag GIT. I think we discussed that release tag should be
> signed, not sure if this is achievable.
Oh, sorry, was confused that tag name pattern is different from beta2.
We should pick one rule and stick to it (I do not really care which).
>
> 28.02.2016 17:21, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>> Hello, all. I've just released 2.02~beta3. The goal of this release is
>> to chase bugs so that we can move to 2.02 release. So from now on if you
>> think that your patch should be included in 2.02 rather than in 2.03,
>> please add [2.02] to the beginning of your email subject
>>
>> The tarball is available at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
>> and signature at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>>
>> Signed with following fingerprint:
>> E53D 497F 3FA4 2AD8 C9B4 D1E8 35A9 3B74 E82E 4209
>>
>> It's also available as a signed tag grub-2.02-beta3 in official git
>> repository.
>>
>> If you don't have xz support alternatively you may consider files
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz
>> and signature at
>> http://alpha.gnu.org/gnu/grub/grub-2.02~beta3.tar.xz.sig
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2016-02-28 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 14:21 2.02~beta3 release Vladimir 'φ-coder/phcoder' Serbinenko
2016-02-28 14:31 ` Andrei Borzenkov
2016-02-28 14:38 ` Vladimir 'phcoder' Serbinenko
2016-02-28 16:40 ` Andrei Borzenkov
2016-02-28 16:44 ` Andrei Borzenkov [this message]
2016-02-29 8:16 ` Vladimir 'phcoder' Serbinenko
2016-03-01 19:10 ` Andrei Borzenkov
2016-03-01 19:14 ` Vladimir 'phcoder' Serbinenko
2016-03-02 10:18 ` Vladimir 'phcoder' Serbinenko
2016-02-29 8:21 ` Vladimir 'phcoder' Serbinenko
2016-02-29 14:41 ` Peter Jones
2016-03-02 15:03 ` Vladimir 'phcoder' Serbinenko
2016-02-29 15:40 ` Konrad Rzeszutek Wilk
2016-03-11 16:02 ` adrian15
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=56D323D3.7040909@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@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 NNTP newsgroup(s).