KolibriOS/kolibrios
15
24
Fork 61
Code Issues 132 Pull Requests 31 Actions Projects 1 Releases Wiki Activity

Remove vestigial SVN files #75

New Issue
Open
opened 2024-06-05 10:27:18 +00:00 by ace-dent · 4 comments
ace-dent commented 2024-06-05 10:27:18 +00:00
Member
Copy Link
Copy Source

When we are 100% happy with the SVN --> git migration...

SVN relies on many duplicate copies of files, that are not needed under git. This bloats the repository size.

  • 1. Remove all files under tag subdirectories (tags have already been setup on Git).
  • 2. Carefully create branches under git, and copy files out of subdirectories into their own branch.
  • 3. Move program files out of trunk subdirectories; fix file path references.
  • 4. Move Kernel files out of trunk subdirectory; fix file path references.
  • 5. Cleanup hardcoded SVN references and comments: SVN, //svn., $SVN, etc.
When we are 100% happy with the SVN --> git migration... SVN relies on many duplicate copies of files, that are not needed under git. This bloats the repository size. - [x] 1. Remove all files under `tag` subdirectories (tags have already been setup on Git). - [ ] 2. Carefully create `branches` under git, and copy files out of subdirectories into their own branch. - [x] 3. Move program files out of `trunk` subdirectories; fix file path references. - [ ] 4. Move Kernel files out of `trunk` subdirectory; fix file path references. - [ ] 5. Cleanup hardcoded SVN references and comments: `SVN`, `//svn.`, `$SVN`, etc.
👍 1
ace-dent added the
Priority
Low
 label 2025-04-05 18:33:33 +00:00
ace-dent added the Category/General
Kind
Build
 labels 2025-05-20 09:02:20 +00:00
Sweetbread referenced this issue from a commit 2025-05-20 15:36:16 +00:00
Post-SVN clean up (#244)
ace-dent commented 2025-06-17 17:14:47 +00:00
Author
Member
Copy Link
Copy Source

Question for the Dev community:

  • Do we want to keep tagged versions of FASM in KolibriOS source code?

We have 1.73, and also SVN tagged versions for 1.68 and 1.71. I propose removing the latter two.

Question for the Dev community: - Do we want to keep tagged versions of FASM in KolibriOS source code? We have [1.73](https://git.kolibrios.org/KolibriOS/kolibrios/src/branch/main/programs/develop/fasm), and also SVN tagged versions for [1.68 and 1.71](https://git.kolibrios.org/KolibriOS/kolibrios/src/branch/main/programs/develop/fasm/tags). I propose removing the latter two.
👍 1
Burer commented 2025-06-17 18:19:48 +00:00
Owner
Copy Link
Copy Source

Do we want to keep tagged versions of FASM in KolibriOS source code?

Maybe it is kept for some compatibility, like old FASM in autobuild toolchain, or something like that.
Otherwise - I don't see practical reason in keeping it. But I may be wrong.

> Do we want to keep tagged versions of FASM in KolibriOS source code? Maybe it is kept for some compatibility, like old FASM in autobuild toolchain, or something like that. Otherwise - I don't see practical reason in keeping it. But I may be wrong.
👍 1
dunkaist commented 2025-06-17 19:41:48 +00:00
Owner
Copy Link
Copy Source

Question for the Dev community:

  • Do we want to keep tagged versions of FASM in KolibriOS source code?

I believe they can be safely removed

> Question for the Dev community: > - Do we want to keep tagged versions of FASM in KolibriOS source code? I believe they can be safely removed
👍 1
ace-dent commented 2025-06-17 20:58:38 +00:00
Author
Member
Copy Link
Copy Source

Thanks @Burer and @dunkaist for feedback. PR raised #268

Thanks @Burer and @dunkaist for feedback. PR raised #268
Burer referenced this issue from a commit 2026-04-20 16:17:04 +00:00
fs/kfar: Post-SVN tidy (#429)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
C
Category/Applications
Category/Drivers
Category/General
Category/Kernel
Category/Libraries
Eolite
FASM
FS
GSoC
This issue in GSoC program
 HardwareTested
HLL
Influence/Settings
Influence/Text/TYPO
IRCC
Kernel
Kind
Breaking
Breaking change that won't be backward compatible
Kind
Bug
Something is not working
Kind
Build
Kind
Documentation
Documentation changes
Kind
Enhancement
Improve existing functionality
Kind
Feature
New functionality
Kind
Security
This is security issue
Kind
Testing
Issue or pull request related to testing
Pay for the code
Paid task
PR
Conflicts
PR conflicts with main
PR
Dependent
This PR is dependent on another PR
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
PR
Ready to merge
Pull request is ready for merge
PR
Request changes
Changes requested in pull request
PR
Review required
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label Category/General
Kind
Build
Priority
Low
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ace-dent (Andrew) Burer Doczom (Mikhail Frolov) dunkaist (Ivan B) Egor00f (Егор) hidnplayr IgorA Leency (Kiril Lipatov) mxlgv (Max Logaev) ramenu rgimad sdongles (Serhii Sakhno) Sweetbread (Gleb Zaharov)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KolibriOS/kolibrios#75
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?