Benjamin_Loison/Verified_repositories
1
0
Fork 0
Code Issues 6 Pull Requests Packages Projects Releases Wiki Activity
6 Commits 1 Branch 0 Tags
f7448055b9b656e70fc3659d45176b33b86a9014
Commit Graph
6 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Benjamin_Loison f7448055b9 Add gitea.lemnoslife.com/Benjamin_Loison/Gitea_instance.json 2023-02-01 00:51:09 +01:00
Benjamin_Loison cddf020b21 Remove unused comment field of gitea.lemnoslife.com/Benjamin_Loison/LemnosLife_Rust 
It's a real debate whether or not to include the field with empty string
to equivalently mean that there isn't any specific comment that the
author wanted to share. To minimize file sizes and improve readability
let's proceed by not specifying default values to fields.
 2023-02-01 00:49:01 +01:00
Benjamin_Loison 66b7e574fb Precise the notion of repository state in README.md 2023-02-01 00:44:53 +01:00
Benjamin_Loison 753bbb8e3f Add gitea.lemnoslife.com/Benjamin_Loison/LemnosLife_Rust 2023-02-01 00:42:14 +01:00
Benjamin_Loison 32263625f5 Precise the current trust level target in README.md 
I thought about adding the following convention:

> Current convention is such that if a folder exists but just contains `.gitkeep`, it means that everything that could fall into this folder and isn't existing is considered as verified.

This would be useful for personal git users, but it's an edge case and
would anyway need to precise an overwhole git user gits hash to confirm
a statement at a given gits state.
So let's keep the same convention for every git.
 2023-02-01 00:38:24 +01:00
Benjamin_Loison fd7ad7a93d Add README.md 2023-01-31 23:43:23 +01:00