| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| |
| | |
This removes the fetchRecurse compiler warnings and makes the
behavior match the other submodule options (i.e. the in-memory
setting can be reset to the on-disk value).
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Leftover OID -> ID changes
|
| | |
| | |
| | |
| | | |
Following the rest of the series, use 'id' when refering to the value.
|
| | |
| | |
| | |
| | |
| | | |
Same as the other commits in the series, we use 'id' when talking about
thing rather than the datatype.
|
| | |
| | |
| | |
| | | |
In the same vein as the previous commits in this series.
|
| | |
| | |
| | |
| | | |
Rename git_tree_entry_byoid() to _byid() as per the convention.
|
| | | |
|
| | |
| | |
| | |
| | | |
This was not converted when we converted the rest, so do it now.
|
| | |
| | |
| | |
| | | |
This was left over when we did the general switch.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
A lot of the tests were checking for overflow, which we don't have
anymore, so we can remove them.
|
| | |
| | |
| | |
| | | |
Again, we already did this internally, so simply remove the conversions.
|
| | |
| | |
| | |
| | |
| | | |
Internally we already did everything with git_bufs, so this is just
exposing those functions with public names.
|
| | |
| | |
| | |
| | |
| | | |
Since we now export that type, we can avoid making the user guess a
size.
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
It's hard or even impossible to correctly free the string buffer
allocated by git_patch_to_str in some circumstances. Drop the function
so people have to use git_patch_to_buf instead - git_buf has a dedicated
destructor.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Returning library-allocated strings from libgit2 works fine on Linux,
but may cause problems on Windows because there is no one C Runtime that
everything links against. With libgit2 not exposing its own allocator,
freeing the string is a gamble.
git_patch_to_str already serializes to a buffer, then returns the
underlying memory. Expose the functionality directly, so callers can use
the git_buf_free function to free the memory later.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
The "merge none" (don't automerge) flag was only to aide in
merge trivial tests. We can easily determine whether merge
trivial resulted in a trivial merge or an automerge by examining
the REUC after automerge has completed.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The default merge_file level was XDL_MERGE_MINIMAL, which will
produce conflicts where there should not be in the case where
both sides were changed identically. Change the defaults to be
more aggressive (XDL_MERGE_ZEALOUS) which will more aggressively
compress non-conflicts. This matches git.git's defaults.
Increase testing around reverting a previously reverted commit to
illustrate this problem.
|
| |
| |
| |
| |
| |
| | |
Extend the "unmodified" submodule workdir test to include
uninitialized submodules, to prevent reporting submodules as
modified when they're not in the workdir at all.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Any well-behaved program should write a descriptive message to the
reflog whenever it updates a reference. Let's make this more prominent
by removing the version without the reflog parameters.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This changes git_signature_dup to actually honor oom conditions raised by
the call to git__strdup. It also aligns it with the error code return
pattern used everywhere else.
|
| | |
|
| | |
|
| |
| |
| | |
Closes #2029
|
|\ \
| | |
| | | |
submodule branch option + little VS2013 fix
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Reference operations with log
|
| | |
| | |
| | |
| | |
| | |
| | | |
The frontend used to look at the file directly, but that's obviously not
the right thing to do. Expose it on the backend and use that function
instead.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Sometimes (e.g. stash) we want to make sure that a log will be written,
even if it's not in one of the standard locations. Let's make that
easier.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This was a convenience method for the refs front-end to do the reflog
writing. This is now done in the backend and it has no more reason for
being.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Whenever a reference is created or updated, we need to write to the
reflog regardless of whether the user gave us a message, so we shouldn't
leave that to the ref frontend, but integrate it into the backend.
This also eliminates the race between ref update and writing to the
reflog, as we protect the reflog with the ref lock.
As an additional benefit, this reflog append on the backend happens by
appending to the file instead of parsing and rewriting it.
|
| | |
| | |
| | |
| | | |
This is as yet unused.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This wasn't being tested and since it has a callback, I fixed it
even though the return value of this callback is not treated like
any of the other callbacks in the API.
|