On Mon, Mar 12, 2012 at 2:28 PM, Alvaro Sanchez <
alvsan09@xxxxxxxxx> wrote:
> Hello Steffen,
> One question related to working with "fast forward only",
> I have not experimented with this option although it seems that the authors
> will need to re-base the local branch before submitting a new patch set.
> If the project is very dynamic and incorporates several changes, would not
> this cause problems to distinguish functionality from the master branch vs
> functionality changes from the previous patch set ?
>
> /Alvaro
>
>
> On Sat, Mar 10, 2012 at 4:04 AM, Steffen Pingel <
steffen.pingel@xxxxxxxxxxx>
> wrote:
>>
>> Hi,
>>
>> the Mylyn Context MFT and Mylyn Reviews R4E projects recently started
>> using the Eclipse.org Gerrit instance. After the Mylyn 3.7 release is
>> out I would like to start using the Eclipse.org Gerrit instance for
>> all Mylyn sub-projects as well (Mylyn, Mylyn Builds, Mylyn Commons,
>> Mylyn Context, Mylyn Docs, Mylyn Incubator, Mylyn Reviews, Mylyn
>> Tasks, Mylyn Versions).
>>
>> I would propose the following settings:
>>
>> * Allow committers to bypass Gerrit
>> * Fast forward only
>> * Require Change-Id in commit message
>>
>> Additionally, I would request trigger jobs on the Eclipse.org Hudson
>> Sandbox instance.
>>
>> Any thoughts? Concerns?
>>
>> Steffen
>>
>> --
>> Steffen Pingel
>> Senior Software Developer, Eclipse Mylyn
>> Mylyn Tasks Lead
>>
http://tasktop.com
>> _______________________________________________
>> mylyn-dev mailing list
>>
mylyn-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>
>
>
> _______________________________________________
> mylyn-dev mailing list
>
mylyn-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>
--
Steffen Pingel
Senior Software Developer, Eclipse Mylyn
Mylyn Tasks Lead
http://tasktop.com
_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-dev