From: Nathan Cutler <ncutler@suse.cz>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: master vs. next
Date: Fri, 15 May 2015 13:15:09 +0200 [thread overview]
Message-ID: <5555D53D.7070400@suse.cz> (raw)
In-Reply-To: <CAOi1vP_PPrMDE9o2Ai78sepPJf6ZH+99UVkiMAkiVMqemwEp3w@mail.gmail.com>
On 2015-05-15 12:45, Ilya Dryomov wrote:
> If you need to fix something that is broken in next, then you target
> next. I'm sure sometimes on an ad-hoc basis commits are cherry-picked
> from master into next or even go directly into next to expedite things,
> but that's rare and not something a newcomer should be concerned about.
SubmittingPatches says to target next for bugfixes. So far I have only
been pushing bugfixes, so I have been targeting that branch. And when
the patch is merged, it goes directly into next. So I don't understand
why you say that's rare and not something I should be concerned about?
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2015-05-15 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 8:44 master vs. next Nathan Cutler
2015-05-15 9:48 ` Ilya Dryomov
2015-05-15 10:04 ` Loic Dachary
2015-05-15 10:45 ` Ilya Dryomov
2015-05-15 11:15 ` Nathan Cutler [this message]
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=5555D53D.7070400@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.