3 ms·
> In the past, the solution was just not to use any of that. A bunch of files inside a random folder in your computer This is what my company does. Except we u
by runnerup 5y ago
> In the past, the solution was just not to use any of that. A bunch of files inside a random folder in your computer
This is what my company does. Except we use git. Everyone just keeps their repo on their drive and there's no central "canonical" repository. Everyone has a personal folder in the main fileserver and they push frequently to their personal remote repo.
Any time they send emails saying they've made a notable milestone, anyone curious just merges against their remote.
The codebases somehow rarely (never) diverge catastrophically. Maybe because we're doing embedded work.
- p1necone 5y agoWhat do you release from - just whatever personal repo has all the features you need? This is interesting because you're kinda using git as the fully distributed system that it's design allows for, which isn't that common.
- runnerup 5y ago> What do you release from - just whatever personal repo has all the features you need? Yep - when we need to release we just kind of merge everything into a release, compile the firmware, validate it in house and then send it to our contract manufacturer in China. "Who" does that depends on whoever is free or most closely tied to that update.
- rightbyte 5y agoThat actually sounds quite nice and quite close how Torvalds thought git would be used I guess.