- 01 Nov, 2013 16 commits
-
-
preserve windows error numbers as well
Vicent Martí committed -
Edward Thomson committed
-
Fix examples to make the important stuff more obvious
Vicent Martí committed -
Warnings for Windows x64 (MSVC) and GCC on Linux
Russell Belfer committed -
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-
Linquize committed
-
indexer: remove the stream infix
Vicent Martí committed -
Vicent Marti committed
-
Vicent Marti committed
-
Ben Straub committed
-
Improve bad URL handling
Vicent Martí committed -
I'm not too happy about manually inserting < and > but those get output as html tags otherwise.
Carlos Martín Nieto committed
-
- 31 Oct, 2013 12 commits
-
-
Seems that regexp in Mac OS X and Linux were behaving differently: while in OS X the empty string didn't match any value, in Linux it was matching all of them, so the the second fetch refspec was overwritting the first one, instead of creating a new one. Using an unmatcheable regular expression solves the problem (and seems to be portable).
Daniel Rodríguez Troitiño committed -
Daniel Rodríguez Troitiño committed
-
At some moment git_config_delete_entry lost the ability to delete one entry of a multivar configuration. The moment you had more than one fetch or push ref spec for a remote you will not be able to save that remote anymore. The changes in network::remote::remotes::save show that problem. I needed to create a new git_config_delete_multivar because I was not able to remove one or several entries of a multivar config with the current API. Several tries modifying how git_config_set_multivar(..., NULL) behaved were not successful. git_config_delete_multivar is very similar to git_config_set_multivar, and delegates into config_delete_multivar of config_file. This function search for the cvar_t that will be deleted, storing them in a temporal array, and rebuilding the linked list. After calling config_write to delete the entries, the cvar_t stored in the temporal array are freed. There is a little fix in config_write, it avoids an infinite loop when using a regular expression (case for the multivars). This error was found by the test network::remote::remotes::tagopt.
Daniel Rodríguez Troitiño committed -
Russell Belfer committed
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
Use gmtime() instead of gmtime_t()
Vicent Martí committed -
The latter is not available on Windows
Linquize committed -
Ben Straub committed
-
- 30 Oct, 2013 12 commits
-
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
Ben Straub committed
-
protocol: basic support for multi_ack_detailed
Vicent Martí committed -
This fixes #1703.
Carlos Martín Nieto committed -
This tells the server that we speak it, but we don't make use of its extra information to determine if there's a better place to stop negotiating. In a somewhat-related change, reorder the capabilities so we ask for them in the same order as git does. Also take this opportunity to factor out a fairly-indented portion of the negotiation logic.
Carlos Martín Nieto committed -
Ben Straub committed
-
Ben Straub committed
-
Carlos Martín Nieto committed
-
It was there to keep it apart from the one which read in from a file on disk. This other indexer does not exist anymore, so there is no need for anything other than git_indexer to refer to it. While here, rename _add() function to _append() and _finalize() to _commit(). The former change is cosmetic, while the latter avoids talking about "finalizing", which OO languages use to mean something completely different.
Carlos Martín Nieto committed -
Ben Straub committed
-