Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index




On 10 Jun 2016, at 15:51, Khaled Hosny <khaledhosny@eglug.org> wrote:

On Fri, Jun 10, 2016 at 03:27:00PM +0200, jan iversen wrote:


On 10 Jun 2016, at 14:39, Khaled Hosny <khaledhosny@eglug.org> wrote:

On Fri, Jun 03, 2016 at 07:20:45PM +0530, Akash Jain wrote:
Therefore I request a feature branch with commit access so I can push
code faster then the current work flow will allow.

Can you we get a Akash commit access to push his work on a branch, he
has sent several patches to gerrit already and I think he can be trusted
with commit access (though in general I’d prefer if there was an
alternative to push his work before it is ready to be merged, but there
does not seem to be any).

How about using gerrit, it is designed for that purpose.

Gerrit does not handle multiple commits quite well, and the code is
still evolving so it will just make everything needlessly complex
(rebasing, squashing commits etc.).

Well, you have rebasing and squashing on a branch as well. Using git commit --amend works very well 
for mutiple commits (and one merge), actually that saves the --squash.

We have a slot in the weekly ESC meeting where new committers are suggested, discussed and normally 
approved.

rgds
jan i


Regards,
Khaled
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.