aboutsummaryrefslogtreecommitdiff
path: root/send-pack.c
Commit message (Collapse)AuthorAge
* Do ref matching on the sender side rather than on receiverLinus Torvalds2005-06-30
| | | | | | | | | | | | 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 packLinus Torvalds2005-06-30
| | | | | | | | 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 doLinus Torvalds2005-06-29
| | | | Me tired.
* Slow but steady progress on git pack receive/sendLinus Torvalds2005-06-29
|
* git-send-pack: start parsing local/remote reference differencesLinus Torvalds2005-06-29
| | | | | Right now it just shows which refs it picks up, and whether they are the same or changed on the remote end. Getting there..
* Make send/receive-pack be closer to doing something interestingLinus Torvalds2005-06-29
|
* Start of "git-send-pack", the local part of sending off a packLinus Torvalds2005-06-29
Like git-receive-pack, this is only partway done.