Re: [eclipse.org-committers] Experience using GitHub verus Eclipse.org H

[Christian Campo <christian.campo@xxxxxxxxxxxx>]

Too me the biggest advantage of Github is the ability to fork and do my own thing. There I can play around and choose what I contribute back using a PR and what I keep for myself. And sure enough I can update my fork with the lastest changes of the master repo and still keep my own stuff for myself. And I have a complete repo and can build from it.

Because sure enough not every PR is accepted by the committers…. (at least not every patch in bugzillla is merged in my experience :-) )

christian

Von: <eclipse.org-committers-bounces@xxxxxxxxxxx> on behalf of "Zivkov, Sasa" <sasa.zivkov@xxxxxxx>
Datum: Donnerstag, 31. März 2016 um 09:37
An: Stefan Oehme <st.oehme@xxxxxxxxx>
Cc: "eclipse.org-committers@xxxxxxxxxxx" <eclipse.org-committers@xxxxxxxxxxx>
Betreff: Re: [eclipse.org-committers] Experience using GitHub verus Eclipse.org Hosted Git

From: Stefan Oehme <st.oehme@xxxxxxxxx>

Am 30.03.2016 um 11:42 schrieb Zivkov, Sasa <sasa.zivkov@xxxxxxx>:

Github's pull requests encourage the fix-up working style: if something needs to be fixed

it is usually done in a new commit on top of the existing commits in the pull request.

You can avoid that by rebasing and squashing commits in the PR as necessary.

Sure it is possible, but it is just not how majority of Github users work... because

fix-up style is the default. This is why I wrote "encourage".

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------