| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
On close, we might get a return code which looks like an error but just
means that the other side closed gracefully. Handle that.
|
| |
|
|
|
| |
Anything SSL is deprecated. Let's make sure we don't try to use SSL v3
when talking to the server.
|
| | |
|
| |
|
|
|
|
| |
Do not automatically fail on a bad certificate, but let the caller
decide. This means we don't need our switch on errors anymore but can
return a string representation from the security framework.
|
| |
|
|
|
| |
This is what it's meant all along, but now we actually have multiple
implementations, it's clearer to use the name of the library.
|
| | |
|
| |
|
|
|
| |
Instead, provide git_tls_stream_new() to ask for the most appropriate
encrypted stream and use it in our HTTP transport.
|
| |
|
|
|
| |
As an alternative to OpenSSL when we're on OS X. This one can actually
take advantage of stacking the streams.
|
| |\
| |
| | |
config_write -- handle duplicate section headers when deleting entries
|
| | |
| |
| |
| |
| |
| |
| |
| | |
If git_config_delete is to work properly in the presence of duplicate section
headers, it cannot stop searching at the end of the first matching section, as
there may be another matching section later.
When config_write is used for deletion (value = NULL), it may only terminate
when the desired key is found or there are no sections left to parse.
|
| | |
| |
| |
| |
| | |
Instead of using a config file in resources, include the config file content to
be tested directly in the test.
|
| | |
| |
| |
| |
| |
| | |
Add a unittest to validate bug #3043, where a duplicate empty config header
could cause deletion of a config entry to fail silently. The bug is currently
unresolved and this test will fail.
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
Closes #2966.
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Fix git_checkout_tree() to do index filemodes correctly on Windows.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The idea...sometimes, a filemode is user-specified via an
explicit git_index_entry. In this case, believe the user, always.
Sometimes, it is instead built up by statting the file system. In
those cases, go with the existing logic we have to determine
whether the file system supports all filemodes and symlinks, and
make the best guess.
On file systems which have full filemode and symlink support, this
commit should make no difference. On others (most notably Windows),
this will fix problems things like:
* git_index_add and git_index_add_frombuffer() should be believed.
* As a consequence, git_checkout_tree should make the filemodes in
the index match the ones in the tree.
* And diffs with GIT_DIFF_UPDATE_INDEX don't write the wrong filemodes.
* And merges, and probably other downstream stuff now fixed, too.
This makes my previous changes to checkout.c unnecessary,
so they are now reverted.
Also, added a test for index_entry permissions from git_index_add
and git_index_add_frombuffer, both of which failed before these changes.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
git_checkout_tree() has some fallback behaviors for file systems
which don't have full support of filemodes. Generally works fine,
but if a given file had a change of type from a 0644 to 0755 (i.e.,
you add executable permissions), the fallback behavior incorrectly
triggers when writing hte updated index.
This would cause a git_checkout_tree() command, even with the
GIT_CHECKOUT_FORCE option set, to leave a dirty index on Windows.
Also added checks to an existing test to catch this case.
|
| |\ \ \ \
| | | | |
| | | | | |
Fix for Issue #3023 tests fail with no network
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Moved offending tests from network to online so they will get skipped
when there is a lack of network connectivity:
-test_online_remotes__single_branch
-test_online_remotes__restricted_refspecs
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
jeffhostetler/jeffhostetler/memleak_windows_tls_data
Attempt to fix Windows TLS memory leak.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Rebase fixes
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`git_rebase_init` and `git_rebase_open` should take a
`git_rebase_options` and use it for future rebase operations on
that `rebase` object.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
git_rebase_commit should return `GIT_EUNMERGED` when unmerged items
exist in the index, per the documentation. Test that this is correct.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In `git_rebase_operation_current()`, indicate when a rebase has not
started (with `GIT_REBASE_NO_OPERATION`) rather than conflating that
with the first operation being in-progress.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Handle invalid multiline configuration
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Don't assume that comment chars are comment chars, they may be (an
attempt to be escaped). If so, \; is not a valid escape sequence,
complain.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Combine unquoting and multiline detection to avoid ambiguity when
parsing.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Make sure to also update delta->nfiles when merging diffs
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
When diffs are generated, the value for the 'nfiles' field of 'git_diff_delta'
will be consistent with the value in the 'status' field. Merging diffs can
modify the 'status' field of some deltas and the 'nfiles' field needs to be
updated accordingly.
|
| |\ \ \ \
| | | | |
| | | | | |
ignore: fix negative ignores without wildcards.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Implement git_submodule_set_branch.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Diff fixes
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In the prior implementation, enabling GIT_DIFF_UPDATE_INDEX would overwrite
entries in the index with the ones generated from scanning the working if the
OID was the same.
Because this OID comparison ignores file modes, this means an file in the
workdir with only an exec bit difference with the one in the index would end
up being overwritten, resulting in the exec bit being loss. There might be
other related bugs but the fix of comparing OIDs and file modes should
address them all.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The variable noid is guaranteed to be zero at this point of the code path.
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|_|_|/ /
|/| | | | | |
| | | | | | |
| | | | | | | |
jeffhostetler/jeffhostetler/memleak_test_core_mkdir
Fix memleak in test/core/mkdir reported by CRTDBG
|
