[fpc-other] Git & SVN

Marco van de Voort marcov at stack.nl
Tue May 23 20:38:49 CEST 2017


In our previous episode, Karoly Balogh (Charlie/SGR) said:
> > Git just doesn't do KISS.
> 
> You need an SVN server to start working with SVN. With Git, you go to a
> directory, do "git init" and start committing. Everything is local. Not
> sure how that's not KISS. (You can add a remote later, and then push to
> it, with the full history intact. This remote can even be an SVN repo.)

The previous discussions were about team use of GIT, to be specific, FPC
core repo.

The problem is that if problems get practical the advocatists suddenly step
back and aren't really able to do more than regurgitate either the standard
beginner "wisdoms" or "you shouldn't want this" or "this is the new improved
ways" or similar platitudes.

To get get back on track, I'll restate the question I posed in the last
message unambigously:

how to avoid that a push of member X doesn't leave a branch in an
undesirable state that leaves member Y three choices:

1. push anyway and make the mess worse
2. hold the commit/push
3. clean the mess himself.

In your own repository that is no problem, and even in companies this only
takes only a few LART/cluebat applications to fix. However in distributed
teams this is a pain.





More information about the fpc-other mailing list