-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
15 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e3764bf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, Max and Timo, for making clear for me what can be improved. I really understand it by your specific example comments about what Blaubart and me have delivered. Now I really got that there was a lack of coherence, transparency, comprehensibility and clarity.
Now I've tried to comply to these necessities by delivering a new branch
https://github.com/7lima/meta-openvario/tree/pull_request_317-branch
on which our work is separated into a handful of commits which should be all well-described and focused. Doing this segmentation of aspects of the code changes I've noticed how important it is to cleanly separate, assemble and describe what has been done - by myself. This was even harder to do at the end of several weeks of collaborative work and about 80 commits that have been produced in a continuous extension and refactoring process.
The results on the branch are the same as before but they hopefully are easier to comprehend and to judge. Note that when you walk though it then just the 7 commits from today are relevant.
I guess @Blaubart will do a new follow-up PR from this one. Thank you all for your partnership!