Re: mimic is forked

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

 



On Fri, May 4, 2018 at 3:54 PM, Ricardo Dias <rdias@xxxxxxxx> wrote:
>
>
> On 04-05-2018 03:57, Sage Weil wrote:
>
>>
>> I retargetted all the mimic branches at the mimic branch (i.e., option 2)
>> but I'm sort of thinking option 1 is less confusing.  Any strong opinions?

yeah, it helps to avoid rebasing these PRs if they were targeting
master, which is in flux.

and i am for option 1 also. as this model is simpler and, yeah, less confusing.

>
>
> +1 to option 1.
>
> From a developer perspective it's easier to have every commit in a single
> branch, specially if some new nautilus feature depends on a mimic bug fix.
>
>>
>>
>
> --
> Ricardo Dias
> Senior Software Engineer - Storage Team
> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> HRB 21284
> (AG Nürnberg)
>
> --
> 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



-- 
Regards
Kefu Chai
--
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