- 06 Jan, 2013 1 commit
-
-
nulltoken committed
-
- 03 Jan, 2013 3 commits
-
-
Vicent Marti committed
-
Ben Straub committed
-
Ben Straub committed
-
- 05 Dec, 2012 1 commit
-
-
Vicent Marti committed
-
- 30 Nov, 2012 1 commit
-
-
Ben Straub committed
-
- 27 Nov, 2012 1 commit
-
-
Ben Straub committed
-
- 18 Nov, 2012 2 commits
-
-
Michael Schubert committed
-
nulltoken committed
-
- 13 Nov, 2012 4 commits
-
-
Returning NULL for the string when we haven't signaled an error condition is counter-intuitive and causes unnecessary edge cases. Return an empty string when asking for a string value for a configuration variable such as '[section] var' to avoid these edge cases. If the distinction between no value and an empty value is needed, this can be retrieved from the entry directly. As a side-effect, this change stops the int parsing functions from segfaulting on such a variable.
Carlos Martín Nieto committed -
'[section] variable' and '[section] variable =' behave differently when parsed as booleans, so we need to store that distinction internally.
Carlos Martín Nieto committed -
We're already in the git_config namespace, there is no need to repeat it.
Carlos Martín Nieto committed -
Michael Schubert committed
-
- 09 Nov, 2012 2 commits
-
-
This fixes some various warnings that showed up in Travis and a couple uses of uninitialized memory and one memory leak.
Russell Belfer committed -
nulltoken committed
-
- 30 Oct, 2012 1 commit
-
-
This adds a new API that allows users to reload the config if the file has changed on disk. A new config callback function to refresh the config was added. The modified time and file size are used to test if the file needs to be reloaded (and are now stored in the disk backend object). In writing tests, just using mtime was a problem / race, so I wanted to check file size as well. To support that, I extended `git_futils_readbuffer_updated` to optionally check file size in addition to mtime, and I added a new function `git_filebuf_stats` to fetch the mtime and size for an open filebuf (so that the config could be easily refreshed after a write). Lastly, I moved some similar file checking code for attributes into filebuf. It is still only being used for attrs, but it seems potentially reusable, so I thought I'd move it over.
Russell Belfer committed
-
- 25 Oct, 2012 2 commits
- 23 Oct, 2012 2 commits
-
-
Added `struct git_config_entry`: a git_config_entry contains the key, the value, and the config file level from which a config element was found. Added `git_config_open_level`: build a single-level focused config object from a multi-level one. We are now storing `git_config_entry`s in the khash of the config_file
yorah committed -
This can occur after a manual modification of a config file.
yorah committed
-
- 12 Aug, 2012 1 commit
-
-
The config file parser was not working right if there was no whitespace between the value name and the equals sign. This fixes that.
Russell Belfer committed
-
- 04 Aug, 2012 1 commit
-
-
This updates all the `foreach()` type functions across the library that take callbacks from the user to have a consistent behavior. The rules are: * A callback terminates the loop by returning any non-zero value * Once the callback returns non-zero, it will not be called again (i.e. the loop stops all iteration regardless of state) * If the callback returns non-zero, the parent fn returns GIT_EUSER * Although the parent returns GIT_EUSER, no error will be set in the library and `giterr_last()` will return NULL if called. This commit makes those changes across the library and adds tests for most of the iteration APIs to make sure that they follow the above rules.
Russell Belfer committed
-
- 21 Jul, 2012 2 commits
-
-
Carlos Martín Nieto committed
-
This allows us to set options like "some.foo\\ish.var". This closes #830
Carlos Martín Nieto committed
-
- 11 Jul, 2012 1 commit
-
-
Adding a new config iteration function that let's you iterate over just the config entries that match a particular regular expression. The old foreach becomes a simple use of this with an empty pattern. This also fixes an apparent bug in the existing `git_config_foreach` where returning a non-zero value from the iteration callback was not correctly aborting the iteration and the returned value was not being propogated back to the caller of foreach. Added to tests to cover all these changes.
Russell Belfer committed
-
- 13 Jun, 2012 2 commits
-
-
Carlos Martín Nieto committed
-
Adam Roben committed
-
- 17 May, 2012 3 commits
-
-
Vicent Martí committed
-
Vicent Martí committed
-
Vicent Martí committed
-
- 02 May, 2012 1 commit
-
-
Vicent Martí committed
-
- 25 Apr, 2012 1 commit
-
-
This limitation was a misparsing of the documentation.
Carlos Martín Nieto committed
-
- 16 Apr, 2012 1 commit
-
-
Variable values may be quoted to include newlines, literal quotes and other characters. Add support for these and test it.
Carlos Martín Nieto committed
-
- 01 Apr, 2012 1 commit
-
-
Ben Straub committed
-
- 09 Mar, 2012 1 commit
-
-
write_section() mistakenly treated is input as the whole variable name instead of simply the section (and possibly subsection) and would confuse "section.subsection" as a section plus variable name and produce a wrong section header. Fix this and include a test for writing "section.subsection.var" and reading it from the file.
Carlos Martín Nieto committed
-
- 05 Mar, 2012 1 commit
-
-
Yes, this is error handling solely for `refs.c`, but some of the abstractions leak all ofer the code base.
Vicent Martí committed
-
- 02 Mar, 2012 2 commits
-
-
This clears up the memory leaks that valgrind seems to find on my machine.
Russell Belfer committed -
It turns out that commit 31e9cfc4cbcaf1b38cdd3dbe3282a8f57e5366a5 did not fix the GIT_USUSED behavior on all platforms. This commit walks through and really cleans things up more thoroughly, getting rid of the unnecessary stuff. To remove the use of some GIT_UNUSED, I ended up adding a couple of new iterators for hashtables that allow you to iterator just over keys or just over values. In making this change, I found a bug in the clar tests (where we were doing *count++ but meant to do (*count)++ to increment the value). I fixed that but then found the test failing because it was not really using an empty repo. So, I took some of the code that I wrote for iterator testing and moved it to clar_helpers.c, then made use of that to make it easier to open fixtures on a per test basis even within a single test file.
Russell Belfer committed
-
- 25 Feb, 2012 1 commit
-
-
Carlos Martín Nieto committed
-
- 17 Feb, 2012 1 commit
-
-
Carlos Martín Nieto committed
-