user/sven/git.git/send-pack.c, branch v1.0rc1

Be careful when dereferencing tags.

2005-11-03T00:50:58Z

One caller of deref_tag() was not careful enough to make sure what deref_tag() returned was not NULL (i.e. we found a tag object that points at an object we do not have). Fix it, and warn about refs that point at such an incomplete tag where needed. Signed-off-by: Junio C Hamano

Ignore funny refname sent from remote

2005-10-15T18:23:40Z

This allows the remote side (most notably, upload-pack) to show additional information without affecting the downloader. Peek-remote does not ignore them -- this is to make it useful for Pasky's automatic tag following. Signed-off-by: Junio C Hamano

Support +: format in push as well.

2005-08-24T23:50:53Z

Signed-off-by: Junio C Hamano

Fix ref_newer() in send-pack.

2005-08-06T06:05:33Z

When more than two references need to be checked with ref_newer() function, the second and later calls did not work correctly. This was because the later calls found commits retained by the "struct object" layer that still had smudges made by earlier calls. Signed-off-by: Junio C Hamano

Fix send-pack for non-commitish tags.

2005-08-05T07:47:56Z

Again I left the v2.6.11-tree tag behind. My bad. This commit makes sure that we do not barf when pushing a ref that is a non-commitish tag. You can update a remote ref under the following conditions: * You can always use --force. * Creating a brand new ref is OK. * If the remote ref is exactly the same as what you are pushing, it is OK (nothing is pushed). * You can replace a commitish with another commitish which is a descendant of it, if you can verify the ancestry between them; this and the above means you have to have what you are replacing. * Otherwise you cannot update; you need to use --force. Signed-off-by: Junio C Hamano

Renaming push.

2005-08-04T00:16:29Z

This allows git-send-pack to push local refs to a destination repository under different names. Here is the name mapping rules for refs. * If there is no ref mapping on the command line: - if '--all' is specified, it is equivalent to specifying ":" for all the existing local refs on the command line - otherwise, it is equivalent to specifying ":" for all the refs that exist on both sides. * is just a shorthand for ":" * ":" push ref that matches to ref that matches . - It is an error if does not match exactly one of local refs. - It is an error if matches more than one remote refs. - If does not match any remote refs, either - it has to start with "refs/"; is used as the destination literally in this case. - == and the ref that matched the must not exist in the set of remote refs; the ref matched locally is used as the name of the destination. For example, - "git-send-pack --all " works exactly as before; - "git-send-pack master:upstream" pushes local master to remote ref that matches "upstream". If there is no such ref, it is an error. - "git-send-pack master:refs/heads/upstream" pushes local master to remote refs/heads/upstream, even when refs/heads/upstream does not exist. - "git-send-pack master" into an empty remote repository pushes the local ref/heads/master to the remote ref/heads/master. Signed-off-by: Junio C Hamano

send-pack: handle partial pushes correctly.

2005-08-03T19:41:12Z

When pushing into multi-user repository, or when pushing to a repository from a local repository that has rebased branches that has been pruned, the destination repository can have head commits that are missing from the local repository. This should not matter as long as the local head of the branch being pushed is a proper superset of the destination branch, but we ended up trying to run rev-list telling it to exclude objects reachable from those heads missing from the local repository, causing it to barf. Prune those heads from the rev-list parameter list, and make sure we do not try to push a branch whose remote head is something we lack. Signed-off-by: Junio C Hamano

Make send-pack --all and explicit ref mutually exclusive.

2005-08-03T05:51:07Z

send-pack had a confusing misfeature that "send-pack --all master" updated all refs, while "send-pack --all" did not do anything. Make --all and explicit refs mutually exclusive, and make sure "send-pack --all" updates all refs. Signed-off-by: Junio C Hamano

Fix potential send-pack SIGSEGV

2005-07-27T05:23:18Z

The check that the source is ahead of the destination incorrectly expects pop_most_recent_commit() to gracefully handle an empty list. Fix by just checking the list itself, rather than the return value of the pop function. [jc: I did the test script that demonstrated the problem] Signed-off-by: Linus Torvalds Signed-off-by: Junio C Hamano

git-send-pack: verify that sender is a proper superset of receiver

2005-07-19T11:03:47Z

This should make sure that if you have multiple people pushing to the same tree, they cannot overwrite each others work, but have to merge before being able to update the common reference tree.