[–] [S] 1 point 4 weeks ago

Thanks for your feedback,I didn't write the bootloader, I use limine,but I write all the features and the kernel by myself, and I am also firstly polishing this feature and making it ready for release(D.eSystem can also run and boot on real hardware). But thanks for your feedback, for 6.1.9 oder 6.2.0 I want to make a whole new github repo.

  • source
  • parent
  • context
  • [–] [S] 2 points 1 month ago

    Hi,nice that you go in kernel dev,D.eSystem itself is not suporting apps or something from outside,but you can go on the github link,download the source code andadd own features to the kernel and you can compile D.eSystem:)

  • source
  • parent
  • context
  • [–] [S] -1 points 1 month ago (2 children)

    Hello,thanks for you feedback,I know the repo is the bigest problem with D.eSystem 6,I have planed to kepthe D.eSystem 6 repo like it is but to create a new repo for D.eSystem 7 when I am starting D.eSystem 7 in future.

  • source
  • parent
  • context
  • [–] [S] 0 points 1 month ago (4 children)

    The tags from v6.0.9 to v6.1.5 currently all point to the same commit because I didnt push the actual development history to GitHub yet.

    I was developing locally and only uploaded the source snapshots as release archives, which makes the tags look incorrect or “fictional”.

    The ISOs are built from newer code, but that code hasn’t been pushed to the repo yet — that’s why the tags don’t match the releases. And the newer code is based off the older code.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago

    You are right, the repo structure isnt in its final form yet. I originally uploaded the full source code as release archives instead of pushing each version as proper commits, which is why the tags currently point to the same snapshot.

    I am reorganizing the repository so every version will have its own commit history, proper tags, and the full source directly in the repo instead of only in releases.

    Im fixing the Git workflow so it follows standard conventions. Thanks for your feedback:)

  • source
  • parent
  • context
  • [–] [S] 2 points 1 month ago (6 children)

    The repo structure is still in progress. I originally uploaded the full source as release packages instead of pushing incremental commits, which is why the tags currently point to the same snapshot. Im reorganizing the repository so each version will have its own commit history and proper tagging.

    The 6.1.5 release is built from the same code as the tag (nothing unpublished.)

    And yes, Im the sole developer. I only use AI for explanations or debugging, not for generating code.

    Im cleaning up the repo structure soon.

  • source
  • parent
  • context
  • view more: next ›