git/send-pack.c, branch v0.99 Mirror of https://git.kernel.org/pub/scm/git/git.git/ https://git.shady.money/git/atom?h=v0.99 2005-07-08T20:58:40Z Teach 'git-send-pack' to send new branches and tags. 2005-07-08T20:58:40Z Linus Torvalds torvalds@g5.osdl.org 2005-07-08T20:58:40Z urn:sha1:584c6cc91a61ec615419452ca540041be6ba9f38 The protocol always supported it, but send-pack didn't actually know how to tell the other side about a new branch/tag. NOTE! You'll have to name it explicitly on the command line: if you don't name any branches, git-send-pack will default to the branches that already exist. Add "git_path()" and "head_ref()" helper functions. 2005-07-05T18:31:32Z Linus Torvalds torvalds@g5.osdl.org 2005-07-05T18:31:32Z urn:sha1:723c31fea2f1c4994de837bda9022ffa8b6de1bb "git_path()" returns a static pathname pointer into the git directory using a printf-like format specifier. "head_ref()" works like "for_each_ref()", except for just the HEAD. Move ref path matching to connect.c library 2005-07-04T20:24:30Z Linus Torvalds torvalds@g5.osdl.org 2005-07-04T20:24:30Z urn:sha1:013e7c7ff498aae82d799f80da37fbd395545456 It's a generic thing for matching refs from the other side. Factor out the ssh connection stuff from send-pack.c 2005-07-04T18:57:58Z Linus Torvalds torvalds@g5.osdl.org 2005-07-04T18:57:58Z urn:sha1:f71925983ddc365c167559ecc623f2c000607cda I want to use it for git-fetch-pack too. Fix gcc warning in send-pack.c 2005-07-03T17:00:01Z Linus Torvalds torvalds@g5.osdl.org 2005-07-03T17:00:01Z urn:sha1:7ec4e60819764128351d526a77859a403c0d4ff4 send_pack() was declared to return "int" (although nobody cared), but didn't actually return anything. Do ref matching on the sender side rather than on receiver 2005-06-30T19:28:24Z Linus Torvalds torvalds@ppc970.osdl.org 2005-06-30T19:28:24Z urn:sha1:d0efc8a71da1855c705fd2074b219bcb158b6dbd This makes the receiver always send a full list of valid refs, which will allow us to do better packs, as well as handle creation of new refs. Eventually. Right now we just moved the matching and enabled it. So now you can do git-send-pack host:path branch1 branch2 to only send branches "branch1" and "branch2". git-send-pack: actually send the object pack 2005-06-30T17:17:39Z Linus Torvalds torvalds@ppc970.osdl.org 2005-06-30T17:17:39Z urn:sha1:94fdb7aa17cc778dff084857192e155aabca86f1 This concludes this lesson. I've actually successfully sent an update using the git-send-pack command. Probably tons of work still to do, and nasty debugging, but it's now actually potentially useful. Add comment on what send-pack still needs to do 2005-06-30T06:07:01Z Linus Torvalds torvalds@ppc970.osdl.org 2005-06-30T06:07:01Z urn:sha1:56b6ed8881f3504b686a254cccdb5aa1a1a9e925 Me tired. Slow but steady progress on git pack receive/send 2005-06-30T05:50:48Z Linus Torvalds torvalds@ppc970.osdl.org 2005-06-30T05:50:48Z urn:sha1:7f8e982834bbc476e73c2ec02ebe8749caef51bc git-send-pack: start parsing local/remote reference differences 2005-06-30T05:31:41Z Linus Torvalds torvalds@ppc970.osdl.org 2005-06-30T05:31:41Z urn:sha1:e4b5c7fff47d3a794249ea2da6b9ec4e33e157f3 Right now it just shows which refs it picks up, and whether they are the same or changed on the remote end. Getting there..