user/sven/git.git/git-parse-remote.sh, branch v1.4.4.4

fetch: get the remote branches to merge from the branch properties

2006-09-24T07:13:49Z

If in branch "foo" and this in config: [branch "foo"] merge=bar "git fetch": fetch from the default repository and program the "bar" branch to be merged with pull. Signed-off-by: Santi Béjar Signed-off-by: Junio C Hamano

Fetch: default remote repository from branch properties

2006-09-24T07:13:49Z

If in branch "foo" and this in config: [branch "foo"] remote=bar "git fetch" = "git fetch bar" "git pull" = "git pull bar" Signed-off-by: Santi Béjar Signed-off-by: Junio C Hamano

fetch, pull: ask config for remote information

2006-05-04T07:07:06Z

Now you can say [remote.junio] url = git://git.kernel.org/pub/scm/git/git.git fetch = next:next in your .git/config. [jc: fixed up the log message that still said "pull" ] Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano

Fix-up previous expr changes.

2006-04-14T02:05:38Z

The regexp on the right hand side of expr : operator somehow was broken. expr 'z+pu:refs/tags/ko-pu' : 'z\+\(.*\)' does not strip '+'; write 'z+\(.*\)' instead. We probably should switch to shell based substring post 1.3.0; that's not bashism but just POSIX anyway. Signed-off-by: Junio C Hamano

Shell utilities: Guard against expr' magic tokens.

2006-04-13T23:45:48Z

Some words, e.g., `match', are special to expr(1), and cause strange parsing effects. Track down all uses of expr and mangle the arguments so that this isn't a problem. Signed-off-by: Mark Wooding Signed-off-by: Junio C Hamano

fetch,parse-remote,fmt-merge-msg: refs/remotes/* support

2006-03-11T06:31:20Z

We can now easily fetch and merge things from heads in the refs/remotes/ hierarchy in remote repositories. The refs/remotes/ hierarchy is likely to become the standard for tracking foreign SCMs, as well as the location of Pull: targets for tracking remote branches in newly cloned repositories. Signed-off-by: Eric Wong Signed-off-by: Junio C Hamano

parse-remote and ls-remote clean-up.

2005-11-25T21:49:17Z

There is no reason to use git-sh-setup from git-ls-remote. git-parse-remote can help the caller to use .git/remotes shortcut if it is run inside a git repository, but can still be useful outside a git repositoryas long as the caller does not use any shortcut. Use "git-rev-parse --git-dir" to figure out where the GIT_DIR is, instead of using git-sh-setup. This also makes "git-ls-remote origin" to work from inside a subdirectory of a git managed repository as a side effect. Signed-off-by: Junio C Hamano

Refuse to create funny refs in clone-pack, git-fetch and receive-pack.

2005-10-15T18:23:39Z

Using git-check-ref-format, make sure we do not create refs with funny names when cloning from elsewhere (clone-pack), fast forwarding local heads (git-fetch), or somebody pushes into us (receive-pack). Signed-off-by: Junio C Hamano

Do not require ls-remote to be run inside a git repository.

2005-10-06T21:10:39Z

The scripts work perfectly without a repository. Signed-off-by: Alex Riesen Signed-off-by: Junio C Hamano

Fix default pull not to do an unintended Octopus.

2005-09-28T23:22:00Z

The refspecs specified in the .git/remotes/ on the "Pull: " lines are for fetching multiple heads in one go, but most of the time making an Octopus out of them is not what is wanted. Make git-fetch leave the marker in .git/FETCH_HEAD file so that later stages can tell which heads are for merging and which are not. Tom Prince made me realize how stupid the original behaviour was. Signed-off-by: Junio C Hamano