{"thread":{"id":"3623","subject":"[PATCH 0/6] http-push updates","startedAt":"2006-03-11T04:17:49Z","lastAt":"2006-03-14T00:28:15Z","messageCount":3,"participants":["Nick Hengeveld","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":6},"messages":[{"id":"17444","messageId":"20060311041749.GB3997@reactrix.com","threadId":"3623","inReplyTo":null,"subject":"[PATCH 0/6] http-push updates","fromName":"Nick Hengeveld","fromEmail":"nickh@reactrix.com","sentAt":"2006-03-11T04:17:49Z","receivedAt":"2006-03-11T04:17:49Z","isPatch":true,"sender":{"key":"nickh@reactrix.com","avatar":null},"body":"This series fixes a few http transport and http-push bugs, includes some\nrefactoring, and adds functionality to update remote server info/refs.\n\nI'm considering future support for initializing a remote repo if the\nremote url points to an empty directory and the --force arg is present.\nAny thoughts?\n\nI'm also planning to add support for using packs to send updates, and\nfor updating remote server objects/info/packs.  I'm not sure whether it\nmakes sense to always send packs or to only do so when enough objects\nneed to be pushed.\n\n-- \nFor a successful technology, reality must take precedence over public\nrelations, for nature cannot be fooled.\n"},{"id":"17504","messageId":"7vek16udg6.fsf@assigned-by-dhcp.cox.net","threadId":"3623","inReplyTo":"20060311041749.GB3997@reactrix.com","subject":"Re: [PATCH 0/6] http-push updates","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-03-13T05:21:45Z","receivedAt":"2006-03-13T05:21:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nick Hengeveld <nickh@reactrix.com> writes:\n\n> I'm considering future support for initializing a remote repo if the\n> remote url points to an empty directory and the --force arg is present.\n> Any thoughts?\n\nRepository maintenance tasks:\n\n - create a new repository\n - create new branch (and new tag) -- I think you can already do this\n - remove an unneeded branch and tag\n - (perhaps) running update-server-info\n - running repack\n\n> I'm also planning to add support for using packs to send updates, and\n> for updating remote server objects/info/packs.  I'm not sure whether it\n> makes sense to always send packs or to only do so when enough objects\n> need to be pushed.\n\nIf you have repack support somehow, always sending packs\n(especially the thin kind) would make sense, but otherwise you\nprobably would want some arrangements to make sure many small\npacks are periodically consolidated into larger smaller number\nof packs, so that they would not fragment the vma of git\nprograms that run on the server side by mmap()ing them into\ntheir address spaces.\n"},{"id":"17534","messageId":"20060314002815.GJ3997@reactrix.com","threadId":"3623","inReplyTo":"7vek16udg6.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH 0/6] http-push updates","fromName":"Nick Hengeveld","fromEmail":"nickh@reactrix.com","sentAt":"2006-03-14T00:28:15Z","receivedAt":"2006-03-14T00:28:15Z","isPatch":true,"sender":{"key":"nickh@reactrix.com","avatar":null},"body":"On Sun, Mar 12, 2006 at 09:21:45PM -0800, Junio C Hamano wrote:\n\n> Repository maintenance tasks:\n> \n>  - create a new repository\n>  - remove an unneeded branch and tag\n>  - running repack\n\nIn a DAV-only server environment, it seems like there are a few\noptions for supporting these tasks:\n\n- extend http-push with additional args and/or local config settings.\n  This approach would be more efficient wrt packs than separate\n  push and repack steps since packs will all need to be created locally\n  and then sent; a combined repack/push operation would mean that new\n  objects will only be sent once as part of a pack.\n\n- add DAV versions of git-init-db/git-branch/git-repack\n\n- extend git-init-db/git-branch/git-repack to be DAV-aware\n\nI like option #1.\n\n>  - create new branch (and new tag) -- I think you can already do this\n\nRight - you can create locally and then push that branch/tag or\n--all/--tags.\n\n>  - (perhaps) running update-server-info\n\nhttp-push already updates info/refs if it existed before the push \n(perhaps that behavior should also be based on a local config setting.)\nI would plan to add support for updating objects/info/packs along with\npack/repack support.  That should be all the server-info there is to\nupdate, right?\n\n-- \nFor a successful technology, reality must take precedence over public\nrelations, for nature cannot be fooled.\n"}]}