| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| | |
ignore: consider files with a CR in their names
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We currently consider CR to start the end of the line, but that means
that we miss cases with CR CR LF which can be used with git to match
files whose names have CR at the end of their names.
The fix from the patch comes from Russell's comment in the issue.
This fixes #2536.
|
| |\ \
| | |
| | | |
Propogate GIT_ENOTFOUND from git_remote_rename
|
| |/ / |
|
| |\ \
| | |
| | | |
Make config reading continue after hitting a missing include file.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Error-handling is cleaned up to only let a file-not-found error
through, not other sorts of errors. And when a file-not-found
error happens, we clean up the error.
* Test now checks that file-not-found introduces no error. And
other minor cleanups.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For example, if you have
[include]
path = foo
and foo didn't exist, git_config_open_ondisk() would just give up
on the rest of the file. Now it ignores the unresolved include
without error and continues reading the rest of the file.
|
| |\ \ \
| |_|/
|/| | |
Changed context_lines and interhunk_lines to uint32_t to match struct s_xdemitconf
|
| | | |
| | |
| | |
| | | |
s_xdemitconf
|
| |\ \ \
| | | |
| | | | |
remote: unify the creation code
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The create function with default refspec is the same as the one with a
custom refspec, but it has the default refspec, so we can create the one
on top of the other.
|
| |\ \ \ \
| | | | |
| | | | | |
netops: return GIT_ECERTIFICATE when it fails the basic tests
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we first ask OpenSSL to verify the certfiicate itself (rather
than the HTTPS specifics), we should also return
GIT_ECERTIFICATE. Otherwise, the caller would consider this as a failed
operation rather than a failed validation and not call the user's own
validation.
|
| |\ \ \ \
| | | | |
| | | | | |
Fix segmentation fault observed on OpenBSD/sparc64
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | | |
A non-readable mapping of a file causes an access violation in
the pack tests. Always use PROT_READ to work around this.
|
| |\ \ \ \
| |/ / /
|/| | | |
Make the Visual Studio compiler happy
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
An anonymous remote wouldn't create remote-tracking branches, so testing
we don't create them for TAGS_ALL is nonsensical. Furthermore, the name
of the supposed remote-tracking branch was also not one which would have
been created had it had a name.
Give the remote a name and test that we only create the tags when we
pass TAGS_ALL and that we do create the remote-branch branch when given
TAGS_AUTO.
|
| |/ /
| |
| |
| |
| | |
Since it's not necessarily obvious, mention the merging state and how to
clear it.
|
| |\ \
| | |
| | | |
revert tests: always use core.autocrlf=false in tests
|
| |/ / |
|
| |\ \
| |/
|/| |
Fixed the most obvious Clang static analyzer warnings
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Flip THREADSAFE's default to ON
|
| | |
| |
| |
| |
| |
| | |
Threads are here to stay; and for a while now, users have had to call
the initialization function which sets up threads and crypto regardless
of whether the library was built threadsafe or not.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| | |
Use size_t for page size, instead of long. Check result of sysconf.
Use size_t for page offset so no cast to size_t (second arg to p_mmap).
Use mod instead div/mult pair, so no cast to size_t is necessary.
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
| |\ \
| | |
| | | |
Rebase (merge)
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Rename git_merge_head to git_annotated_commit, as it becomes used
in more operations than just merge.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Already cherry-picked commits should not be re-included. If all changes
included in a commit exist in the upstream, then we should error with
GIT_EAPPLIED.
|
| | | |
| | |
| | |
| | | |
Commit the current patch of a rebase process.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
`git_rebase_next` will apply the next patch (or cherry-pick)
operation, leaving the results checked out in the index / working
directory so that consumers can resolve any conflicts, as appropriate.
|