🏡 index : ~doyle/chartered.git

author Jordan Doyle <jordan@doyle.la> 2021-08-31 2:47:47.0 +01:00:00
committer GitHub <noreply@github.com> 2021-08-31 2:47:47.0 +01:00:00
commit
05dad164153f1d4dd9b4acecfc5bcb2bb6a11eea [patch]
tree
c1c129f35c69383a1f5a2445ec49e02777c8b1c1
parent
625e45d9131cd0858cff40a67636566768bc994a
download
05dad164153f1d4dd9b4acecfc5bcb2bb6a11eea.tar.gz

typo



Diff

 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e5c1b10..d089bda 100644
--- a/README.md
+++ a/README.md
@@ -11,7 +11,7 @@

- ~reverse engineer & create tokio codec for the git protocol~ **now successfully generating a repo, tree & blob in memory git clients can understand!**
- clean up all the hacked-together code and package it all up into a nice library for generating git commit objects etc
- ~serve cargo manifest over git (how does git handle 'force pushes' from server -> client? lets see how they like it for once, i'm sick of people picking on servers all the time)~ **turns out, very well - they've helpfully included the --force flag in their `cargo fetch` call so we can serve a completely different commit on every pull if we wanted to and not have to worry about conflicts**
- ~serve cargo manifest over git (how does git handle 'force pushes' from server -> client? lets see how they like it for once, i'm sick of people picking on servers all the time)~ **turns out, very well - they've helpfully included the --force flag in their `git fetch` call so we can serve a completely different commit on every pull if we wanted to and not have to worry about conflicts**
- serve .crate files over http using auth tokens we generated while serving the manifest

#### open q's