| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/libgit2/libgit2/issues/3866
Has been applied in all Julia builds since 2017:
https://github.com/JuliaLang/julia/pull/17459
Authored-by: Keno Fischer <kfischer@college.harvard.edu>
|
|\
| |
| | |
Handle Win32 shares
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Git for Windows does some truly bizarre things with
paths that start with a forward slash; and expects you
to escape that with `%(prefix)`. This syntax generally
means to add the prefix that Git was installed to -- eg
`/usr/local` -- unless it's an absolute path, in which
case the leading `%(prefix)/` is just removed. And Git
for Windows expects you to use this syntax for absolute
Unix-style paths (in "Git Bash" or Windows Subsystem for
Linux).
Worse, the behavior used to be that a leading `/` was
not absolute. It would indicate that Git for Windows
should add the prefix. So `//` is required for absolute
Unix-style paths. Yes, this is truly horrifying.
Emulate that behavior, I guess, but only for absolute
paths. We won't deal with the Git install prefix. Also,
give WSL users an escape hatch where they don't have to
think about this and can use the literal path that the
filesystem APIs provide (`//wsl.localhost/...`).
|
| |
| |
| |
| |
| |
| |
| | |
With some paths on Win32, we cannot identify the owner because it's on a
file share (WSL2 or UNC). In that case, don't fail, but identify that
the current user does not own the path. This matches Git for Windows
behavior.
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
stash: partial stash specific files
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
`git_strarray_copy` is deprecated (and has been included in
`deprecated.h` for some time). It should not have remained in
the public `strarray.h`. Remove it.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
SHA256: more SHA256 support
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This is much of the plumbing for the object database to support SHA256,
and for objects to be able to parse SHA256 versions of themselves.
|
| | |
| | |
| | |
| | | |
Teach the packfile machinery to cope with SHA256.
|
| | |
| | |
| | |
| | |
| | | |
Ensure that we maintain the `core.repositoryFormatVersion` value instead
of always overwriting it with the default.
|
| | |
| | |
| | |
| | |
| | | |
Provide an internal function to set the repository's `objectformat`,
both in the internal object and in the configuration.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Teach the repository about the `objectformat` extension, supporting
`sha1` always and `sha256` when the experimental sha256 support is
active.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Support the notion of a home directory separately from global configuration directory
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some callers -- like our test suite and the test suites of our language
bindings -- want to isolate the home directory to avoid accidentally
including the executing user's actual home directory data.
Previously, we combined the notion of a home directory and global
configuration -- now that this is separated, we provide users the
ability to configure both.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Users can specify a config file to be included in the home directory
using `~/filename` syntax. Instead of looking in the global
configuration location (which may be overridden), use the user's
_actual_ home directory. This allows callers to change the global
configuration location separately from the home directory.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Users can specify an attribute file to be included in the home
directory using `~/filename` syntax. Instead of looking in the
global configuration location (which may be overridden), use the
user's _actual_ home directory. This allows callers to change the
global configuration location separately from the home directory.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I spent an hour banging my head against this, when it was because the
remote didn't trust my key.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use `git_sysdir_find_homedir_file` to identify the path to the home
directory's `.ssh/known_hosts`; this takes Windows paths into account by
preferring `HOME`, then falling back to `HOMEPATH` and `USERPROFILE`
directories.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Provide a mechanism to look up the user's home directory, using the same
mechanism that we use for locating the global configuration path (a
fancy name for saying "the home directory").
SSH known hosts lookups now use this, instead of simply looking at the
HOME environment variable, to support Windows-style home directory
lookups in `HOME`, `HOMEPATH`, or `USERPROFILE`.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
The windows sysdir functions are libgit2-specific and for git
compatibility only; remove them from the shared util directory and bring
them into the libgit2 source tree.
|
|\ \ \
| | | |
| | | | |
#6422: handle dangling symbolic refs gracefully
|
| | | | |
|
|\ \ \ \ |
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
Fixes issue #6156.
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
|\ \ \ \
| | | | |
| | | | | |
Fix build failure with -DEMBED_SSH_PATH
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
diff_file: Fix crash when freeing a patch representing an empty untracked file
|
| | |/ /
| |/| |
| | | |
| | | | |
This prevents GIT_MMAP_VALIDATE from failing.
This also prevents git_diff_file_content__unload from attempting to free git_str__initstr.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Try to load OpenSSL 3 libraries when compiled with OpenSSL-Dynamic
support.
Handle the deprecated symbol renaming of SSL_get_peer_certificate to
SSL_get1_peer_certificate -- try to load the old name and if it fails,
use the new one.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
When we fail to initialize the OpenSSL subsystem, don't assume that
we're "initialized". Subsequent initialization requests -- if there are
any -- should replay initialization and fail again.
|