From: Nathan Cutler <ncutler@suse.cz>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: ceph-devel@vger.kernel.org
Subject: Re: upstream/firefly exporting the same snap 2 times results in different exports
Date: Wed, 22 Jul 2015 12:27:11 +0200 [thread overview]
Message-ID: <55AF6FFF.5080104@suse.cz> (raw)
In-Reply-To: <55AF405B.4050602@profihost.ag>
On 2015-07-22 09:03, Stefan Priebe - Profihost AG wrote:
> That would be really important. I've seen that this one was already in
> upstream/firefly-backports. What's the purpose of that branch?
That is where the Stable Releases and Backports team stages backports
and does integration testing on them before they are merged into the
'firefly' named branch.
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
prev parent reply other threads:[~2015-07-22 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 12:29 upstream/firefly exporting the same snap 2 times results in different exports Stefan Priebe - Profihost AG
2015-07-21 14:32 ` Jason Dillaman
2015-07-21 16:55 ` Stefan Priebe
2015-07-21 17:19 ` Jason Dillaman
2015-07-21 19:22 ` Stefan Priebe
2015-07-21 19:46 ` Josh Durgin
2015-07-21 19:48 ` Stefan Priebe
2015-07-21 20:48 ` Jason Dillaman
2015-07-21 19:52 ` Stefan Priebe
2015-07-21 20:50 ` Josh Durgin
2015-07-22 7:03 ` Stefan Priebe - Profihost AG
2015-07-22 10:27 ` Nathan Cutler [this message]
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=55AF6FFF.5080104@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.