EverestLinux/libglacier
2
0
Fork 0
Code Issues 3 Pull Requests Packages Projects 1 Releases Wiki Activity

Separate functions from libglacier.c into different files #8

New Issue
Closed
opened 2024-12-31 12:15:07 -05:00 by lw-everestlinux · 1 comment
lw-everestlinux commented 2024-12-31 12:15:07 -05:00
Owner
Copy Link

For example:

  • config.c
  • data.c
  • log.c
  • pkgops.c
  • runtime.c
  • security.c
For example: - config.c - data.c - log.c - pkgops.c - runtime.c - security.c
lw-everestlinux added the enhancement label 2024-12-31 12:15:07 -05:00
lw-everestlinux added this to the libglacier v4.0.0 project 2024-12-31 12:15:07 -05:00
arco-everestlinux was assigned by lw-everestlinux 2025-01-14 15:44:20 -05:00
lw-everestlinux changed reference from release/v4.0.4-rc to patch/v0.1.0-rc 2025-01-14 15:51:49 -05:00
lw-everestlinux commented 2025-02-18 10:10:36 -05:00
Author
Owner
Copy Link

Splitting would cause too many maintainability issues in regards to linking, will put this on hold indefinitely

Splitting would cause too many maintainability issues in regards to linking, will put this on hold indefinitely
Sign in to join this conversation.
patch/v0.1.0-rc
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project libglacier v4.0.0
Assignees
Clear assignees
arco-everestlinux lw-everestlinux
No Assignees arco-everestlinux
1 Participants
Notifications
Due Date
No due date set.
Blocks
#9 Implement unit testing and new Makefile in preparation for patch v0.1.0
EverestLinux/libglacier
Reference: EverestLinux/libglacier#8
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?