Re: master vs. next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 15, 2015 at 2:15 PM, Nathan Cutler <ncutler@xxxxxxx> wrote:
> 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

That's what the first sentence in the paragraph you quoted says.

> why you say that's rare and not something I should be concerned about?

Here I was referring to when something that isn't strictly a bugfix
goes to next or when something goes to master intentionally or by
mistake and then cherry-picked into next by Sage or others after
discussion.  The point I was trying to make is that *that* is something
out of the ordinary and hence something that newcomers don't have to
worry about so much.

Thanks,

                Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux