openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Geissler <geissonator@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Kurt Taylor <kurt.r.taylor@gmail.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: gerrit server update coming - 2.15.2
Date: Wed, 11 Jul 2018 13:55:03 -0500	[thread overview]
Message-ID: <CALLMt=qo1wqBNzy5msu6sh=iXkmL3=a=qWWzVtz2zhaw23Tvig@mail.gmail.com> (raw)
In-Reply-To: <1531319763.4184525.1437335200.4879B6DE@webmail.messagingengine.com>

On Wed, Jul 11, 2018 at 9:36 AM Andrew Jeffery <andrew@aj.id.au> wrote:
>
> On Wed, 11 Jul 2018, at 21:40, Andrew Geissler wrote:
> > On Tue, Jul 10, 2018 at 4:33 PM krtaylor <kurt.r.taylor@gmail.com> wrote:
> > >
> > > On 7/10/18 3:13 PM, Andrew Geissler wrote:
> > >
> > > I'm planning a gerrit update in the near future (this Saturday
> > > maybe?).  Anyone have any issues with an update (or know of any issues
> > > with the 2.15 release)?
> > >
> > > OpenStack is still on 2.13.9+ (we're at 2.14.7), is there a problem we need fixed? No issues, just curious.
> >
> > A few months ago someone asked when I was doing the next update
>
> "Someone"!?
>
> I'm crushed!

Hahaha, sorry, should have remembered, you got the best name out there! :)
Andrew

Andrew

  reply	other threads:[~2018-07-11 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 20:13 gerrit server update coming - 2.15.2 Andrew Geissler
2018-07-10 21:14 ` Gunnar Mills
2018-07-10 21:37   ` Gunnar Mills
2018-07-10 21:33 ` krtaylor
2018-07-11 12:10   ` Andrew Geissler
2018-07-11 14:36     ` Andrew Jeffery
2018-07-11 18:55       ` Andrew Geissler [this message]
2018-07-16 17:54 ` Fwd: " Andrew Geissler
     [not found] <5D23E7CAADD3BE4A97642792FFC691C561C748CB@MBX215.d.ethz.ch>
2018-07-17 12:17 ` Andrew Geissler

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='CALLMt=qo1wqBNzy5msu6sh=iXkmL3=a=qWWzVtz2zhaw23Tvig@mail.gmail.com' \
    --to=geissonator@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=kurt.r.taylor@gmail.com \
    --cc=openbmc@lists.ozlabs.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).