{"thread":{"id":"12475","subject":"[PATCH 0/3] Server side automatic tag following","startedAt":"2008-03-04T02:35:51Z","lastAt":"2008-03-04T02:35:51Z","messageCount":1,"participants":["Shawn O. Pearce"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"70869","messageId":"20080304023550.GL8410@spearce.org","threadId":"12475","inReplyTo":null,"subject":"[PATCH 0/3] Server side automatic tag following","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-03-04T02:35:51Z","receivedAt":"2008-03-04T02:35:51Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"As promised earlier, this series adds automatic tag following on\nthe server side, allowing git-fetch to grab tags over a single\nconnection rather than opening a secondary one for the tags we\ncannot get via my 'sp/fetch-optim' branch.\n\n  1)  git-pack-objects: Automatically pack annotated tags if object was packed\n  2)  Teach fetch-pack/upload-pack about --auto-follow-tags\n  3)  Teach git-fetch to exploit server side automatic tag following\n\n Documentation/git-fetch-pack.txt   |    8 +++-\n Documentation/git-pack-objects.txt |    5 ++\n builtin-fetch-pack.c               |    9 +++-\n builtin-fetch.c                    |    3 +\n builtin-pack-objects.c             |   24 +++++++++-\n fetch-pack.h                       |    3 +-\n t/t5305-autofollow-tag.sh          |   84 ++++++++++++++++++++++++++++++++++++\n t/t5503-tagfollow.sh               |   26 +++++++++++\n transport.c                        |    5 ++\n transport.h                        |    3 +\n upload-pack.c                      |   10 +++-\n 11 files changed, 172 insertions(+), 8 deletions(-)\n\n\nWe may still want to support multiple request/pack pairs on a single\nconnection, but I think that's more work than this is and may not\noffer a worthwhile pay-off.  Usually the client knows what branches\nit wants when it connects, and if it wants tag data.  That's all\nwe need to know on the server to generate an optimal packfile, and\nsaid packfile is the only thing the client needs to update itself.\n\nThe multiple request/pack pairs is actually better implemented for\nusers like X.org where you want to update many repositories over\na single SSH connection.  For that we need git-fetch to multiplex\nover multiple repositories, not just git-upload-pack.\n\n-- \nShawn.\n"}]}