From d34786c3a41030d42e892443cf95b2111091ebdf Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Sat, 31 Jul 2021 16:19:52 -0300 Subject: TODOs.md: Clean up Perl links from Resources --- TODOs.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/TODOs.md b/TODOs.md index c0b7178..dcaa63f 100644 --- a/TODOs.md +++ b/TODOs.md @@ -82,10 +82,13 @@ Benchmark on (stagit): - Nixpkgs: 275k commits, 2.5GB repository - Linux: 1M commits, 2,5GB repository + # Bugs + # Improvements + # Questions ## TODO How to embed repositories without using submodules {#question-5414aee2-031a-5759-2a22-d572ee899ac0} @@ -97,6 +100,7 @@ I want to embed repositories so that I can use them in unit and integration tests, but making them submodules makes the repository much less standalone than I would like. + # Decisions ## DONE Perl vs C {#decision-d349b5be-3e00-4e00-a110-0eb7f402d4ab} @@ -116,9 +120,8 @@ The binary application that will be the CLI could be written in any language, al So the question of Perl vs C now is becoming applicable only on more specific scenarios: when having a `libsomething.so` isn't worth anything. This isn't the case for this library. + # Resources -- -- # Scratch -- cgit v1.2.3