From: Nathan Cutler <ncutler@suse.cz>
To: ceph-devel@vger.kernel.org
Subject: master vs. next
Date: Fri, 15 May 2015 10:44:25 +0200 [thread overview]
Message-ID: <5555B1E9.3010003@suse.cz> (raw)
I'm a newcomer to the ceph project. SubmittingPatches says to target
next for bugfixes and master for features. Beyond that I only have the
vaguest notion of what the next branch is for and how patches get moved
back and forth between master and next. Can anyone comment?
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next reply other threads:[~2015-05-15 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 8:44 Nathan Cutler [this message]
2015-05-15 9:48 ` master vs. next Ilya Dryomov
2015-05-15 10:04 ` Loic Dachary
2015-05-15 10:45 ` Ilya Dryomov
2015-05-15 11:15 ` Nathan Cutler
2015-05-15 11:40 ` Ilya Dryomov
2015-05-15 10:23 ` Joao Eduardo Luis
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=5555B1E9.3010003@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.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.