| Age | Commit message (Collapse) | Author |
|---|
|
Might help scenarios like http://stackoverflow.com/questions/22468146/
|
|
This tells mono to load the debug information and lets the unit testing
framework show stack traces with line numbers in them, which is quite
handy.
|
|
Fix #536
|
|
|
|
fix other non-virtual GetEnumerators
the simplest thing that works
simpler still
when in Rome…
|
|
This is so it can be faked in unit tests.
|
|
Prettifing the message includes:
* Removing empty lines from the beginning and end.
* Removing trailing spaces from every line.
* Turning multiple consecutive empty lines between paragraphs into just one empty line.
* Ensuring the commit message ends with a newline.
* Removing every line starting with "#".
Note that this has nothing to do with the core.autocrlf option.
|
|
|
|
|
|
|
|
Prevents the creation of a default fetch refspec beside the passed in one.
|
|
Added `/d` to xcopy so that files are only copied if newer, saving a few seconds of unnecessary I/O on build.
|
|
|
|
|
|
|
|
Bring initial merge functionality to LibGit2Sharp.
|
|
|
|
|
|
|
|
This has the nice side effect of allowing binary changes
to be detected.
|
|
|
|
Github recently (25th of december, 2013) changed its handling of the include-tag option. Skipping tests while waiting for a proper solution to be found.
Same thing as libgit2/libgit2#2020
|
|
|
|
|
|
https://github.com/libgit2/libgit2/compare/96fb6a6...65e9dc6
|
|
|
|
|
|
|
|
|
|
|
|
Implemented as an extension method of `ObjectDatabase`.
Lots of logic taken from [archive-tar.c](https://github.com/git/git/blob/master/archive-tar.c).
|
|
The resulting `TarWriter` file is a low-level abstraction that can be used to write tar files.
Included:
- only keep a unique `TarWriter` file
- merging `UsTarHeader` and `TarHeader`, and adding them as private classes of `TarWriter`
- removal of unneeded `Write` overloads
Some changes to the tar format has been included to better comply with the one described here: http://en.wikipedia.org/wiki/Tar_%28computing%29#Format_details
|
|
This commit adds [tar-cs](http://code.google.com/p/tar-cs/) to LibGit2Sharp without any modifications to the original source code.
|
|
|
|
Added Network.Fetch(Remote, IEnumerable<string>, [FetchOptions]) overload to allow for custom refspecs to
be fetched. The refspecs are used only temporarily and not stored in the configuration.
Fixes #572.
|
|
Changed the signature to Network.Fetch(Remote, FetchOptions). As of
#536, optional parameters should be grouped in a xxxOptions type.
Network.Fetch() has currently 5 optional parameters, and a sixth one
(RefSpecs) will be introduced soon.
|
|
|
|
Now that this is doable directly inside the revision walker, let's
expose it as a possible filter option.
This fixes #258.
|
|
This is our implementation of in-memory remotes. Ask the repository to
fetch/list from a url instead of a remote.
|
|
We already have the refspecs parsed the git_remote, and loading them
lazily means we'll be parsing them again, and possibly parse a different
set from the ones we used to have loaded.
Make the loading eager, and pass the RemoteSafeHandle to more places, as
we need to use it in order to provide a single snapshot of the data.
|
|
|
|
Fix #562
|
|
|
|
|
|
|
|
https://github.com/libgit2/libgit2/compare/98eaf39...96fb6a6
|
|
Renames in status require more detailed data than simply paths, in
order to collect old path, new path and similarity data. Use
git_status_list to collect this data and use a new StatusEntry to
store it.
|
|
Push/Pull Ref Specs can be updated via Remotes.Update(). The collections
can either be manipulated or replaced completely. Any changes are saved
immediately.
|
|
|
|
this is a tiny modification for spell mistake.
orig:
Ensure.ArgumentNotNullOrEmptyString(thirdKeyPart, "secondKeyPart");
now:
Ensure.ArgumentNotNullOrEmptyString(thirdKeyPart, "thirdKeyPart");
|
