git/connect.c, branch v0.99.8a

Merge refs/heads/portable from http://www.cs.berkeley.edu/~ejr/gits/git.git

2005-08-29T06:02:01Z

Support +: format in push as well.

2005-08-24T23:50:53Z

Signed-off-by: Junio C Hamano

Fix ?: statements.

2005-08-24T03:41:12Z

Omitting the first branch in ?: is a GNU extension. Cute, but not supported by other compilers. Replaced mostly by explicit tests. Calls to getenv() simply are repeated on non-GNU compilers. Signed-off-by: Jason Riedy

Use GIT_SSH environment to specify alternate ssh binary.

2005-08-10T05:28:20Z

[jc: I ended up rewriting Martin's patch due to whitespace breakage, but the credit goes to Martin for doing the initial patch to identify what needs to be changed.] Signed-off-by: Martin Sivak Signed-off-by: Junio C Hamano

[PATCH] -Werror fixes

2005-08-10T05:28:19Z

GCC's format __attribute__ is good for checking errors, especially with -Wformat=2 parameter. This fixes most of the reported problems against 2005-08-09 snapshot.

send-pack: allow generic sha1 expression on the source side.

2005-08-06T17:19:38Z

This extends the source side semantics to match what Linus suggested. An example: $ git-send-pack kernel.org:/pub/scm/git/git.git pu^^:master pu would allow me to push the current pu into pu, and the commit two commits before it into master, on my public repository. The revised rule for updating remote heads is as follows. $ git-send-pack [--all] [...] - When no is specified: - with '--all', it is the same as specifying the full refs/* path for all local refs; - without '--all', it is the same as specifying the full refs/* path for refs that exist on both ends; - When one or more s are specified: - a single token (i.e. no colon) must be a pattern that tail-matches refs/* path for an existing local ref. It is an error for the pattern to match no local ref, or more than one local refs. The matching ref is pushed to the remote end under the same name. - : can have different cases. is first tried as the tail-matching pattern for refs/* path. - If more than one matches are found, it is an error. - If one match is found, must either match no remote ref and start with "refs/", or match exactly one remote ref. That remote ref is updated with the sha1 value obtained from the sha1. - If no match is found, it is given to get_extended_sha1(); it is an error if get_extended_sha1() does not find an object name. If it succeeds, must either match no remote ref and start with "refs/" or match exactly one remote ref. That remote ref is updated with the sha1 value. Signed-off-by: Junio C Hamano

send-pack: allow the same source to be pushed more than once.

2005-08-06T17:19:38Z

The revised code accidentally inherited the restriction that a reference can be pushed only once, only because the original did not allow renaming. This is no longer necessary so lift it. Signed-off-by: Junio C Hamano

Fix refname termination.

2005-08-05T23:50:54Z

When a new ref is being pushed, the name of it was not terminated properly. Signed-off-by: Junio C Hamano

[PATCH] Fix sparse warnings

2005-08-04T04:41:56Z

fix one 'should it be static?' warning and two 'mixing declarations and code' warnings. Signed-off-by: Alecs King 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