Tortoisegit updating to revision


Unknown arguments are passed directly to , returns the corresponding git commit hash (this can optionally be followed by a tree-ish to specify which branch should be searched). This relies on your imported fetch data being up-to-date.When given a tree-ish, returns the corresponding SVN revision number. This makes absolutely no attempts to do patching when committing to SVN, it simply overwrites files with those specified in the tree or commit.If an SVN revision has a property, "svm:headrev", it is likely that the revision was created by SVN:: Mirror (also used by SVK).The property contains a repository UUID and a revision.The value of this option must match one of the paths specified by a --branches (or --tags) option.



filter-branch also allows reformatting of metadata for ease-of-reading and rewriting authorship info for non-"svn.authors File" users.It will automatically create a directory based on the basename of the URL passed to it; or if a second argument is passed; it will create a directory and work within that.It accepts all arguments that the Commit each diff from a specified head directly to the SVN repository, and then rebase or reset (depending on whether or not there is a diff between SVN and head).Normally this command initializes the current directory. Each of these flags can point to a relative repository path (--tags=project/tags) or a full url (--tags=https://foo.org/project/tags).

You can specify more than one --tags and/or --branches options, in case your Subversion repository places tags or branches under multiple paths.

If this option is specified, for each SVN committer name that does not exist in the authors file, the given file is executed with the committer name as the first argument.