…ion doesn't change.
…e to Repository
was adding a \n at the end of the file.
Compiling from the solution files generates a non-versioned assembly for simplicity of build setup. Compiling from the nant build script generates properly versioned assemblies.
…e unit tests.
…ry or file. * StatusTests.cs: Add tests for the new status operations. * Repository.cs: * RepositoryStatus.cs: * StatusCommand.cs: Implement new operations for getting the status of a specific directory or file. * Leaf.cs: New property for getting the core entry. * Tree.cs: Added missing null check.
… it edits a project that was created with VS2008. VS2008 is when Microsoft changed the path variable from MSBuildBinPath to MSBuildToolsPath and MonoDevelop still uses MSBuildBinPath.
Winterdom.IO.FileMap, since this isn't our default way of packing a file and there isn't any reason to invest in developing a cross-platform replacement. We're leaving the rest of the logic in place in case we decide to invest in this in the future. This was never tested thoroughly and caused tests to fail when it did run.
…he new Commit files operation.
RefName property, which returns the full ref name. This name is required for the update operation. * Branch.cs: Strip the .git dir from the branch name. Added UpstreamStouce, which can be used to set the remote branch that this branch is tracking. Implemented Delete and Rename.
provided files, ignoring what's in the index.
…ed. As a side note, I did confirm that this was only happening when building with Mono from SVN. Building with 2.6.x resulted in no errors.
…eing public. Test now passes without any other modifications.
…vert the code back to the way it was when fixed. Created bug report located here: https://bugzilla.novell.com/show_bug.cgi?id=618539