From: Ken Dreyer <kdreyer@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Ceph tag v0.94.1.1 etc.
Date: Mon, 4 May 2015 11:17:57 -0400 (EDT) [thread overview]
Message-ID: <1294313931.8466302.1430752677295.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5545F3F3.8030206@dachary.org>
Hi Loic,
These are tags on the rhcs-* branches. These branches and tags more-or-less indicate what we're shipping Red Hat's "Ceph Storage" product downstream, which is basically a fork of 0.80.8 and 0.94.1.
Instead of keeping these branches in an internal repository behind Red Hat's firewall I figured I would push them to the public GitHub repository instead, since that fits with certain aspects of the way that Inktank used to build its downstream product. (Re-using the same Jenkins build system upstream and downstream).
I don't know how long we'll keep to this model; it's just the one that works for the moment. I realize this mixes downstream and upstream in a way that's a bit unconventional.
- Ken
----- Original Message -----
> From: "Loic Dachary" <loic@dachary.org>
> To: "Ceph Development" <ceph-devel@vger.kernel.org>
> Sent: Sunday, May 3, 2015 4:09:55 AM
> Subject: Ceph tag v0.94.1.1 etc.
>
> Hi,
>
> At https://git.ceph.com/?p=ceph.git there are tags such as
>
> v0.94.1.1
> v0.80.8.1
>
> etc.
>
> What are they ?
>
> Cheers
>
> --
> Loïc Dachary, Artisan Logiciel Libre
>
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-04 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 10:09 Ceph tag v0.94.1.1 etc Loic Dachary
2015-05-04 15:17 ` Ken Dreyer [this message]
2015-05-04 15:56 ` Loic Dachary
2015-05-12 17:34 ` Loic Dachary
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=1294313931.8466302.1430752677295.JavaMail.zimbra@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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 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.