http-push updates
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | http-push: fix revision walkhttp-push.c | +5 | 0 replies | |
| 2/6 | HTTP slot reuse fixeshttp-push.c http.c http.h | +47 | 0 replies | |
| 3/6 | http-push: refactor remote file/directory processinghttp-push.c | +107 | 0 replies | |
| 4/6 | http-push: improve remote lock managementhttp-push.c | +76 | 0 replies | |
| 5/6 | http-push: support for updating remote info/refshttp-push.c | +536 | 0 replies | |
| 6/6 | http-push: cleanuphttp-push.c | +30 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] http-push updates
This series fixes a few http transport and http-push bugs, includes some refactoring, and adds functionality to update remote server info/refs.
I'm considering future support for initializing a remote repo if the remote url points to an empty directory and the --force arg is present. Any thoughts?
I'm also planning to add support for using packs to send updates, and for updating remote server objects/info/packs. I'm not sure whether it makes sense to always send packs or to only do so when enough objects need to be pushed.
Signature · 2 lines
For a successful technology, reality must take precedence over public relations, for nature cannot be fooled.