delta/libgit2.git/src/remote.c, branch ethomson/mwindow_init

remote: Handle missing config values when deleting a remote

2016-07-15T17:47:01+00:00

Somehow I ended up with the following in my ~/.gitconfig:
[branch "master"]
remote = origin
merge = master
rebase = true

I assume something went crazy while I was running the git.git tests
some time ago, and that I never noticed until now.

This is not a good configuration, but it shouldn't cause problems. But
it does. Specifically, if you have this in your config, and you
perform the following set of actions:

create a remote
fetch from that remote
create a branch off of the remote master branch called "master"
delete the branch
delete the remote

The remote delete fails with the message "Could not find key
'branch.master.rebase' to delete". This is because it's iterating over
the config entries (including the ones in the global config) and
believes that there is a master branch which must therefore have these
config keys.

https://github.com/libgit2/libgit2/issues/3856

Remove unused static functions

2016-06-21T05:58:33+00:00

fetch: Fixed spurious update callback for existing tags.

2016-06-14T20:46:12+00:00

proxy: ask the user for credentials if necessary

2016-04-19T11:54:19+00:00

remote: set error code in `create_internal`

2016-02-23T11:07:36+00:00

Set the error code when an error occurs in any of the called
functions. This ensures we pass the error up to callers and
actually free the remote when an error occurs.

Copy custom_headers insteach of referencing the caller's copy

2015-09-25T14:16:30+00:00

These can be static

2015-09-24T14:32:29+00:00

Avoid segfault when opts == NULL

2015-09-10T18:16:39+00:00

Accept custom headers for fetch too

2015-09-10T12:34:35+00:00

Tell the git_transport about the custom_headers

2015-09-08T18:02:33+00:00