Yes, I read doc but I wanted to be sure that I got it correctly :) For me
we can try such approach.

+1

On Wed, Aug 5, 2015 at 11:06 AM, Dawid Pakuła <[email protected]> wrote:

> Hi,
>
> instead of creating “Merge …” commit it rebase and fast forward. As you
> said, without additional build.
>
> Gerrit doc:
> https://gerrit-review.googlesource.com/Documentation/project-configuration.html#submit_type
>
>
> --
> Dawid Pakuła
> +48 795 996 064
>
> On 5 Aug 2015 at 11:02:35, Michał Niewrzał ([email protected]) wrote:
>
> Hi,
>
> How this will change the flow? Even if given patch is not rebased we will
> just submit change and no need to start one additional build after manual
> rebase?
>
> Michal
>
> On Wed, Aug 5, 2015 at 12:41 AM, Dawid Pakuła <[email protected]> wrote:
>
>> Hi Team,
>>
>> I thinking about changing gerrit submit type setting from "merge if
>> necessary" to "rebase if necessary”,  to avoid manually rebasing before
>> merge.
>>
>> What you think?
>>
>> --
>> Dawid Pakuła
>> +48 795 996 064
>>
>> _______________________________________________
>> pdt-dev mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>>
>
> _______________________________________________
> pdt-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
>
> _______________________________________________
> pdt-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
_______________________________________________
pdt-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev

Reply via email to