| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| | |
We say that you can link libgit2 "unmodified"... "without having to release
its source code". Clarify that you can modify libgit2 - but you must
release _its_ source code back - and you can link libgit2 without having
to release _your software's_ source code.
|
|\ \
| |/
|/| |
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.
|
|\ \
| |/
|/| |
#6491: Sets oid_type on repos open with git_repository_open_bare
|
| | |
|
|/ |
|
|\
| |
| | |
stash: update strarray usage
|
|/ |
|
|\
| |
| | |
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.
|
|\ \
| | |
| | | |
Fix some warnings in main
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
clone: clean up options on failure
|
|/ / |
|
|\ \
| | |
| | | |
SHA256: more SHA256 support
|
| | |
| | |
| | |
| | | |
The git included with xenial is ancient, and lacks sha256 support.
|
| | |
| | |
| | |
| | |
| | | |
The longest path within a git repository is now a SHA256 format
packfile. Adjust our max length checking to match.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
In clar, an underscore is meaningful; avoid using it incorrectly /
unnecessarily.
|
| | |
| | |
| | |
| | | |
This is a conversion of the testrepo.git to SHA256 support.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We provide `BUILD_PATH` to our build script; provide it and mutate
`PATH` when running our tests as well.
We were previously using `cygpath` to try to convert a _list_ of Windows
paths into cygwin / Unix style `PATH` format. This does not work -- it
treats the path list as a single path (with semicolons -- understandably
as those are allowed characters in a Windows path).
For example, `C:\One;C:\Two;C:\Three` is converted to
`/c/one;c:/two;c:/three`.
Add a new function to convert path lists, so that paths are split by
semicolon and fed to `cygpath` independently, then re-joined with a
colon. This means that our example `C:\One;C:\Two;C:\Three` is correctly
converted to `/c/one:/c/two:/c/three`.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We provide `BUILD_PATH` to our build script; provide it and mutate
`PATH` when running our tests as well.
|