| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
A rule can only negate something which was explicitly mentioned in the
rules before it. Change our parsing to ignore a negative rule which does
not negate something mentioned in the rules above it.
While here, fix a wrong allocator usage. The memory for the match string
comes from pool allocator. We must not free it with the general
allocator. We can instead simply forget the string and it will be
cleaned up.
|
| |\
| |
| | |
Spelling fixes
|
| | | |
|
| |\ \
| |/
|/| |
init: return the number of initializations
|
| | | |
|
| |\ \
| |/
|/| |
Add missing else directive
|
| | |
| |
| |
| |
| | |
Add missing else directive to fix compiler warning: control reaches
end of non-void function
|
| |/ |
|
| | |
|
| |\
| |
| | |
peel: reject bad queries with EPEEL
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are some combination of objects and target types which we know
cannot be fulfilled. Return EINVALIDSPEC for those to signify that there
is a mismatch in the user-provided data and what the object model is
capable of satisfying.
If we start at a tag and in the course of peeling find out that we
cannot reach a particular type, we return EPEEL.
|
| | |
| |
| |
| | |
Valgrind is now clean except for libssl and libgcrypt.
|
| |\ \
| | |
| | | |
Fix for misleading "missing delta bases" error.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
That's a bad assumption to make, even though right now it holds
(because of the way we've implemented decompression of packfiles),
this may change in the future, given that ODB objects can be
binary data.
Furthermore, the ODB object can return a NULL pointer if the object
is empty. Copying the NULL pointer to the strbuf lets us handle it
like an empty string. Again, the NULL pointer is valid behavior because
you're supposed to check the *size* of the object before working
on it.
|
| | | | |
|
| |\ \ \
| |/ /
| | | |
Fix for memory leak issue in indexer.c, that surfaces on windows
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| | |
This is a contract that we made in the library and that we need to uphold. The
contents of a blob can never be NULL because several parts of the library (including
the filter and attributes code) expect `git_blob_rawcontent` to always return a
valid pointer.
|
| |\ \
| | |
| | | |
Update message for error during push
|
| | | |
| | |
| | |
| | |
| | |
| | | |
When attempting to update a reference on a remote during push, and the
reference on the remote refers to a commit that does not exist locally,
then we should report a more clear error message.
|
| |\ \ \
| | | |
| | | | |
Clarify the git_remote_ls() documentation
|
| | | |/
| |/|
| | |
| | |
| | | |
Make it clear that this is not the ls-remote command but a way to access
the data we have and how long it's kept around.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we fetch twice with the same remote object, we did not properly
clear the connection flags, so we would leak state from the last
connection.
This can cause the second fetch with the same remote object to fail if
using a HTTP URL where the server redirects to HTTPS, as the second
fetch would see `use_ssl` set and think the initial connection wanted to
downgrade the connection.
|
| |\ \
| | |
| | | |
Provide a convenience function `git_remote_push()`
|
| | | |
| | |
| | |
| | |
| | | |
If the user does not pass any refspecs to push, try to use those
configured via the configuration or via add_push().
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This function, similar in style to git_remote_fetch(), performs all the
steps required for a push, with a similar interface.
The remote callbacks struct has learnt about the push callbacks, letting
us set the callbacks a single time instead of setting some in the remote
and some in the push operation.
|
| |\ \ \
| | | |
| | | | |
Fixed active_refspecs field not initialized on new git_remote objects
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When creating a new remote, contrary to loading one from disk,
active_refspecs was not populated. This means that if using the new
remote to push, git_push_update_tips() will be a no-op since it
checks the refspecs passed during the push against the base ones
i.e. active_refspecs. And therefore the local refs won't be created
or updated after the push operation.
|
| |\ \ \
| | | |
| | | | |
push: use the common refspec parser
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| |\ \ \ \
| |_|/ /
|/| | | |
Fixed a couple Clang warnings
|
| | | |/
| |/| |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
This describes their purpose better, as we now initialize ssl and some
other global stuff in there. Calling the init function is not something
which has been optional for a while now.
|
| | | |
|
| |\ \
| | |
| | | |
Refactor fetchhead
|
| | | |
| | |
| | |
| | | |
This is an ugly chunk of code, so let's put it into its own function.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the remote is anonymous, then we cannot check for any configuration,
as there is no name. Check for this before we try to use the name, which
may be a NULL pointer.
This fixes #2697.
|
| | | |
| | |
| | |
| | |
| | | |
This reduces the clutter somewhat and lets us see what we're asking
about the reference.
|
| | | |
| | |
| | |
| | | |
This gets the value from branch.<foo>.remote.
|
| |\ \ \
| | | |
| | | | |
remote: rename _load() to _lookup()
|
| | |/ /
| | |
| | |
| | | |
This brings it in line with the rest of the lookup functions.
|
| |\ \ \
| | | |
| | | | |
odb: hardcode the empty blob and tree
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
git hardocodes these as objects which exist regardless of whether they
are in the odb and uses them in the shell interface as a way of
expressing the lack of a blob or tree for one side of e.g. a diff.
In the library we use each language's natural way of declaring a lack of
value which makes a workaround like this unnecessary. Since git uses it,
it does however mean each shell application would need to perform this
check themselves.
This makes it common work across a range of applications and an issue
with compatibility with git, which fits right into what the library aims
to provide.
Thus we introduce the hard-coded empty blob and tree in the odb
frontend. These hard-coded objects are checked for before going to the
backends, but after the cache check, which means the second time they're
used, they will be treated as normal cached objects instead of creating
new ones.
|
| |/ /
| |
| |
| |
| |
| | |
This function has one output but can match multiple files, which can be
unexpected for the user, which would usually path the exact path of the
file he wants the status of.
|
