All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: branches
Date: Fri, 18 Jan 2013 20:02:08 +0100	[thread overview]
Message-ID: <50F99C30.7030205@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1301181031130.8622@cobra.newdream.net>

Hi,

what's bobtail-next then? bobtail itself also contains already updates 
since 056.1?

Stefan

Am 18.01.2013 19:32, schrieb Sage Weil:
> I went ahead and made this change last week.
>
> Just a remind, the new world order is:
>
>> master
>>   - active development
>> next
>>   - frozen for next release
>>   - bug fixes only
>>   - regularly merged back into master
>> last
>>   - last release (instead of 'testing')
>>   - packages at /debian-testing and /debian-last, /rpm-testing, /rpm-last
>> bobtail
>>   - bobtail backport series 0.56.x
>>   - packages at /debian-bobtail (and /debian, until cuttlefish),
>>     /rpm-bobtail, /rpm
>> argonaut
>>   - argonaut backport series 0.48.x
>>   - packages at /debian-argonaut
>
> sage
> --
> 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
>

  reply	other threads:[~2013-01-18 19:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 18:39 branches Sage Weil
2013-01-08 18:48 ` branches Mark Nelson
2013-01-18 18:32 ` branches Sage Weil
2013-01-18 19:02   ` Stefan Priebe [this message]
2013-01-18 19:36     ` branches Sage Weil
2013-01-18 21:06       ` branches Nick Couchman

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=50F99C30.7030205@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.com \
    /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.