How does the source1 source2 source3 thing work in the source tree

[edwin-oetelaar]

Why are there multiple directories.
The source3 only contains an OBJECT file no code.
Why are there object files in the repository anyway, this should be source code only right?
This is a version controlled system, I do not think you need to work like this.

[elektor-labs]

That object file is about the most important file of the project and for which we do not have the source code (but thank you for telling us how we should organise our projects).

[edwin-oetelaar]

I was not cynical in my remark, just curious.
I found this repo because I wanted to use a Atmega48PB and I have it running now. (all in 4 KB flash)
Git has the ability to use branching and keep things clean, to merge files and commits into a nice looking source tree with full traceability for who needs that.

The tree reminds me of my old development system before I started using a version control system. Zip files with version numbers in it, directories with cryptical names (and no mention of it in the readme, so you can never remove them because you might break something, object files here and there, you know..).
I just found this :
7bf8a00
A commit without any serious description about what or why changing about 199 files.
Please say that you think it is not funny ;-)
It reminds me of the old days. (nostalgia)