- 22 May, 2015 1 commit
-
-
When we find out that we're dealing with a matching refspec, we set the flag and return immediately. This leaves the strings as NULL, which breaks the contract. Assign these pointers to a string with the correct values.
Carlos Martín Nieto committed
-
- 10 Mar, 2015 1 commit
-
-
If a refspec could not be parsed, the git_refspec__parse function would return an error value but would not provide additional error information for the callers. This commit amends that function to set a more useful error message.
Adrien Thebo committed
-
- 09 Nov, 2014 1 commit
-
-
There is one well-known and well-tested parser which we should use, instead of implementing parsing a second time. The common parser is also augmented to copy the LHS into the RHS if the latter is empty. The expressions test had to change a bit, as we now catch a bad RHS of a refspec locally.
Carlos Martín Nieto committed
-
- 21 Aug, 2014 1 commit
-
-
Jacques Germishuys committed
-
- 17 Aug, 2014 1 commit
-
-
Jacques Germishuys committed
-
- 04 Jul, 2014 2 commits
-
-
We used to assume a refspec would only have an asterisk in the middle of their respective pattern. This has not been a valid assumption for some time now with git. Instead of assuming where the asterisk is going to be, change the logic to treat each pattern as having two halves with a replacement bit in the middle, where the asterisk is.
Carlos Martín Nieto committed -
When transforming a non-pattern refspec, we simply need to copy over the opposite string. Move that logic up to the wrapper so we can assume a pattern refspec in the transformation function.
Carlos Martín Nieto committed
-
- 27 Jan, 2014 1 commit
-
-
Carlos Martín Nieto committed
-
- 01 Nov, 2013 1 commit
-
-
This allows us to add e.g. "HEAD" as a refspec when none are given without overwriting the user's data.
Carlos Martín Nieto committed
-
- 01 Jul, 2013 1 commit
-
-
Russell Belfer committed
-
- 30 Apr, 2013 1 commit
-
-
Carlos Martín Nieto committed
-
- 28 Apr, 2013 1 commit
-
-
Relax the ONELEVEL ref naming rules so the refspec parsing code can ask for 'master' to be considered valid.
Carlos Martín Nieto committed
-
- 20 Apr, 2013 2 commits
-
-
It used to be separate as an attempt to make the querying easier, but it didn't work out that way, so put all the data together. Add git_refspec_string() as well to get the original string, which is now stored alongside the independent parts.
Carlos Martín Nieto committed -
A remote can have a multitude of refspecs. Up to now our git_remote's have supported a single one for each fetch and push out of simplicity to get something working. Let the remotes and internal code know about multiple remotes and get the tests passing with them. Instead of setting a refspec, the external users can clear all and add refspecs. This should be enough for most uses, though we're still missing a querying function.
Carlos Martín Nieto committed
-
- 11 Feb, 2013 2 commits
-
-
Jameson Miller committed
-
Jameson Miller committed
-
- 11 Jan, 2013 1 commit
-
-
Fix libgit2/libgit2sharp#247
nulltoken committed
-
- 08 Jan, 2013 1 commit
-
-
Edward Thomson committed
-
- 11 Nov, 2012 1 commit
-
-
Edward Thomson committed
-
- 25 Oct, 2012 1 commit
-
-
nulltoken committed
-
- 07 Oct, 2012 1 commit
-
-
nulltoken committed
-
- 30 Sep, 2012 1 commit
-
-
The latter shouldn't be exposed and isn't used, git_refspec__parse supersedes it. Fix a leak in the refspec tests while we're at it.
Carlos Martín Nieto committed
-
- 25 Sep, 2012 1 commit
-
-
nulltoken committed
-
- 29 May, 2012 1 commit
-
-
nulltoken committed
-
- 17 May, 2012 2 commits
-
-
Vicent Martí committed
-
Vicent Martí committed
-
- 03 May, 2012 1 commit
-
-
Vicent Martí committed
-
- 30 Apr, 2012 1 commit
-
-
nulltoken committed
-
- 26 Apr, 2012 1 commit
-
-
Carlos Martín Nieto committed
-
- 06 Mar, 2012 1 commit
-
-
This also includes droping `git_buf_lasterror` because it makes no sense in the new system. Note that in most of the places were it has been dropped, the code needs cleanup. I.e. GIT_ENOMEM is going away, so instead it should return a generic `-1` and obviously not throw anything.
Vicent Martí committed
-
- 13 Feb, 2012 1 commit
-
-
Signed-off-by: schu <schu-github@schulog.org>
schu committed
-
- 31 Jan, 2012 1 commit
-
-
git_refspec_transform_r assumed that the reference name passed would be only a branch or tag name. This is not the case, and we need to take into consideration what's in the refspec's source to know how much of the prefix to ignore.
Carlos Martín Nieto committed
-
- 18 Jan, 2012 1 commit
-
-
transport: prevent git_remote_download() from segfaulting when being passed a lightweight remote built with git_remote_new()
nulltoken committed
-
- 08 Dec, 2011 1 commit
-
-
This converts virtually all of the places that allocate GIT_PATH_MAX buffers on the stack for manipulating paths to use git_buf objects instead. The patch is pretty careful not to touch the public API for libgit2, so there are a few places that still use GIT_PATH_MAX. This extends and changes some details of the git_buf implementation to add a couple of extra functions and to make error handling easier. This includes serious alterations to all the path.c functions, and several of the fileops.c ones, too. Also, there are a number of new functions that parallel existing ones except that use a git_buf instead of a stack-based buffer (such as git_config_find_global_r that exists alongsize git_config_find_global). This also modifies the win32 version of p_realpath to allocate whatever buffer size is needed to accommodate the realpath instead of hardcoding a GIT_PATH_MAX limit, but that change needs to be tested still.
Russell Belfer committed
-
- 18 Nov, 2011 1 commit
-
-
A simple branchname as refspec is valid and we shouldn't throw an error when encountering one. Signed-off-by: Carlos Martín Nieto <carlos@cmartin.tk>
Carlos Martín Nieto committed
-
- 29 Oct, 2011 1 commit
-
-
Ensure that all memory related functions (malloc, calloc, strdup, free, etc) are using their respective `git__` wrappers.
Vicent Marti committed
-
- 08 Oct, 2011 1 commit
-
-
It's rare for a configured remote, but for one given as an URL on the command line, it's more often than not the case. Signed-off-by: Carlos Martín Nieto <carlos@cmartin.tk>
Carlos Martín Nieto committed
-
- 19 Sep, 2011 1 commit
-
-
There were quite a few places were spaces were being used instead of tabs. Try to catch them all. This should hopefully not break anything. Except for `git blame`. Oh well.
Vicent Marti committed
-
- 18 Sep, 2011 1 commit
-
-
1. The license header is technically not valid if it doesn't have a copyright signature. 2. The COPYING file has been updated with the different licenses used in the project. 3. The full GPLv2 header in each file annoys me.
Vicent Marti committed
-
- 26 Jun, 2011 1 commit
-
-
Signed-off-by: Carlos Martín Nieto <carlos@cmartin.tk>
Carlos Martín Nieto committed
-