> Just a quick answer: I've seen some teams who have tried employing this "one
> branch for each customer" strategy.
That's called Software Product Lines, and it works best (for various
definitions of "best") with...
- a core of common code
- satellites of custom code
- wall to wall unit tests that test each customization
- the differences extracted to metadata, NOT to git branches
- anything more than 2 clients need migrates to the core.
Put another way, git is not a replacement for metadata configurations
that turn features on and off.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at