summaryrefslogtreecommitdiff
path: root/receive-pack.c
AgeCommit message (Collapse)AuthorFilesLines
2005-07-08Make "upload-pack" match git-fetch-pack usageLibravatar Linus Torvalds1-3/+1
Do the default "try xyz.git xyz fails" thing for the directory we get passed in.
2005-07-06[PATCH] Let umask do its work upon filesystem object creation.Libravatar Junio C Hamano1-1/+1
IIRC our strategy was to let the users' umask take care of the final mode bits. This patch fixes places that deviate from it. Signed-off-by: Junio C Hamano <junkio@cox.net> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-07-03Fix sparse warnings.Libravatar Linus Torvalds1-1/+1
Mainly making a lot of local functions and variables be marked "static", but there was a "zero as NULL" warning in there too.
2005-07-03Fix up "for_each_ref()" to be more usable, and use it in git-fsck-cacheLibravatar Linus Torvalds1-1/+1
It needed to take the GIT_DIR information into account, something that the original receive-pack usage just never cared about.
2005-07-02Generalize the "show each ref" code in receice-packLibravatar Linus Torvalds1-53/+6
This turns it into a generic "do xyz for each ref" library function.
2005-06-30Do ref matching on the sender side rather than on receiverLibravatar Linus Torvalds1-36/+7
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".
2005-06-30Add support for "forcing" a ref on the remote sideLibravatar Linus Torvalds1-2/+18
A "old ref" of all zeroes is considered a "don't care" ref, and allows us to say "write the new ref regardless of what the old ref contained (or even if it existed at all)". This allows (if git-send-pack were to do it) creating new refs, and fixing up old ones.
2005-06-30git-receive-pack: implement ref switch command handlingLibravatar Linus Torvalds1-5/+59
After unpacking the object pack successfully, we go through the list of refs, and verify that they still contain their expected values. Then we replace them with the new ones.
2005-06-29git-receive-pack: start parsing ref update commandsLibravatar Linus Torvalds1-17/+35
We don't act on them yet, but we parse them.
2005-06-29Slow but steady progress on git pack receive/sendLibravatar Linus Torvalds1-2/+4
2005-06-29Make send/receive-pack be closer to doing something interestingLibravatar Linus Torvalds1-119/+7
2005-06-29Add first cut at "git-receive-pack"Libravatar Linus Torvalds1-0/+321
It's not working yet, but it's at the point where I want to be able to track my changes. The theory of operation is that this is the "remote" side of a "git push". It can tell us what references the remote side has, receives out reference update commands and a pack-file, and can execute the unpacking command.