[fpc-other] Git & SVN

[Florian Klämpfl]

Am 25.05.2017 um 00:18 schrieb Graeme Geldenhuys:
> On 2017-05-24 21:07, Florian Klämpfl wrote:
>>> I'm sorry to bust your bubble, but how different can compiler
>>> development be.
>>
>> Apparently it is:
> 
> Then why are you still talking to me.

To avoid that people get the impression we do not know what we are doing (or not doing).

> 
>> The workflow will not change. If the tool does not fit the workflow,
>> it is the wrong tool. Period.
> 
> Yes, habits (good or bad) are a hard thing to break. In that case, please enjoy your project further
> with SubVersion. Until you actually use a project with Git (not git-svn), we might talk again. 

To close this for now and ever: I am using hg at least since 2008 and git at least since 2011 when
it got popular on windows (both natively), hg daily for several periods. And overall the experience
collected during this is for sure a reason (besides others!) why using a dvcs for FPC development is
not a good thing.

And let me also state when we can open is discussion again:

Either
- FPC gets that much "third party" contributions that managing and merging them gets a problem of
the scm, we are light years away from this point though.
or
- Somebody pops up who has the time and motivation to push and to do(!) the migration. This does not
mean to do a half baked conversion of the fpc-svn but the whole process, e.g. starting with a wiki
page collecting all issues and working out solutions, adapting all scripts for release building
etc., fixing all snapshot and regression test machines and it ends up with helping the low traffic
contributors to get their work committed (and pushed!). This is at least one month of work I (and
probably nobody else) can and want to spent.