grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: 2.02~beta3 release
Date: Tue, 1 Mar 2016 22:10:11 +0300	[thread overview]
Message-ID: <56D5E913.3090306@gmail.com> (raw)
In-Reply-To: <CAEaD8JPE9tO6FFHn1UJQsotzfSg2BoXT3hRfoZNUd13PWNAYWw@mail.gmail.com>

29.02.2016 11:16, Vladimir 'phcoder' Serbinenko пишет:
> On Sunday, February 28, 2016, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> 
>> 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).
>>
>> I added signed tag in both formats now. Thank you for reminder.
> 


Something is strange.

bor@bor-Latitude-E5450:~/src/grub$ git log -n2 grub-2.02-beta3
commit b4fc7bc2fdfbcb726e9094d8b1848b393364de77
Merge: c4748ea 8207874
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 15:22:52 2016 +0100

    Merge branch 'master' into next

commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 03:07:41 2016 +0100

    Release 2.02~beta3

bor@bor-Latitude-E5450:~/src/grub$ git log -n2 master
commit d017ea8ede3f76aaf6b6c9dabe3e96af0eebd395
Author: Andrei Borzenkov <arvidjaar@gmail.com>
Date:   Sun Feb 28 21:52:08 2016 +0300

    NEWS update

commit 8207874e5d0d05159fd8c531c87f0f6e4653b8a6
Author: Vladimir Serbinenko <phcoder@gmail.com>
Date:   Sun Feb 28 03:07:41 2016 +0100

    Release 2.02~beta3


I expected tag to point to commit
8207874e5d0d05159fd8c531c87f0f6e4653b8a6 on master.



  reply	other threads:[~2016-03-01 19:10 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
2016-02-29  8:16     ` Vladimir 'phcoder' Serbinenko
2016-03-01 19:10       ` Andrei Borzenkov [this message]
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=56D5E913.3090306@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).