neulab/tldr huggingface dataset:
-d<path>, --destination=<path> If more than one --branches (or --tags) option was given to the init or clone command, you must provide the location of the branch (or tag) you wish to create in the SVN repository. <path> specifies which path to use to create the branch or tag and should match the pattern on the left-hand side of one of the configured branches or tags refspecs. You can see these refspecs with the commands
git config --get-all svn-remote.<name>.branches git config --get-all svn-remote.<name>.tags
where <name> is the name of the SVN repository as specified by the -R option to init (or "svn" by default).
--username Specify the SVN username to perform the commit as. This option overrides the username configuration property.
--commit-url Use the specified URL to connect to the destination Subversion repository. This is useful in cases where the source SVN repository is read-only. This option overrides configuration property commiturl.
git config --get-all svn-remote.<name>.commiturl
--parents Create parent folders. This parameter is equivalent to the parameter --parents on svn cp commands and is useful for non-standard repository layouts.
tag Create a tag in the SVN repository. This is a shorthand for branch -t.
log This should make it easy to look up svn log messages when svn users refer to -r/--revision numbers.
The following features from ‘svn log’ are supported:
-r <n>[:<n>], --revision=<n>[:<n>] is supported, non-numeric args are not: HEAD, NEXT, BASE, PREV, etc ...
-v, --verbose it’s not completely compatible with the --verbose output in svn log, but reasonably close.
--limit=<n> is NOT the same as --max-count, doesn’t count merged/excluded commits
--incremental supported
New features:
--show-commit shows the Git commit sha1, as well
--oneline our version of --pretty=oneline
Note SVN itself only stores times in UTC and nothing else. The regular svn client converts the UTC time to the local time (or based on the TZ= environment). This command has the same behaviour. Any other arguments are passed directly to git log
blame Show what revision and author last modified each line of a file. The output of this mode is format-compatible with the output of ‘svn blame’ by default. Like the SVN blame command, local uncommitted changes in the working tree are ignored; the version of the file in the HEAD revision is annotated. Unknown arguments are passed directly to git blame.
--git-format Produce output in the same format as git blame, but with SVN revision numbers instead of Git commit hashes. In this mode, changes that haven’t been committed to SVN (including local working-copy edits) are shown as revision 0.
find-rev When given an SVN revision number of the form rN, returns the corresponding Git commit hash (this can optionally be followed by a tree-ish to specify which branch should be searched). When given a tree-ish, returns the corresponding SVN revision number.
-B, --before Don’t require an exact match if given an SVN revision, instead find the commit corresponding to the state of the SVN repository (on the current branch) at the specified revision.
-A, --after Don’t require an exact match if given an SVN revision; if there is not an exact match return the closest match searching forward in the history.
set-tree You should consider using dcommit instead of this command. Commit specified commit or tree objects to SVN. This relies on your imported fetch data being up to date. This makes absolutely no attempts to do patching when committing to SVN, it simply overwrites files with those specified in the tree or commit. All merging is assumed to have taken place independently of git svn functions.
create-ignore Recursively finds the svn:ignore property on directories and creates matching .gitignore files. The resulting files are staged to be committed, but are not committed. Use -r/--revision to refer to a specific revision.
show-ignore Recursively finds and lists the svn:ignore property on directories. The output is suitable for appending to the $GIT_DIR/info/exclude file.
mkdirs Attempts to recreate empty directories that core Git cannot track based on information in $GIT_DIR/svn/<refname>/unhandled.log files. Empty directories are automatically recreated when using "git svn clone" and "git svn rebase", so "mkdirs" is intended for use after commands like "git checkout" or "git reset". (See the svn-remote.<name>.automkdirs config file option for more information.)
commit-diff Commits the diff of two tree-ish arguments from the command-line. This command does not rely on being inside a git svn init-ed repository. This command takes three arguments, (a) the original tree to diff against, (b) the new tree result, (c) the URL of the target Subversion repository. The final argument (URL) may be omitted if you are working from a git svn-aware repository (that has been init-ed with git svn). The -r<revision> option is required for this.
The commit message is supplied either directly with the -m or -F option, or indirectly from the tag or commit when the second tree-ish denotes such an object, or it is requested by invoking an editor (see --edit option below).
-m <msg>, --message=<msg> Use the given msg as the commit message. This option disables the --edit option.
-F <filename>, --file=<filename> Take the commit message from the given file. This option disables the --edit option.
info Shows information about a file or directory similar to what ‘svn info’ provides. Does not currently support a -r/--revision argument. Use the --url option to output only the value of the URL: field.
proplist Lists the properties stored in the Subversion repository about a given file or directory. Use -r/--revision to refer to a specific Subversion revision.
propget Gets the Subversion property given as the first argument, for a file. A specific revision can be specified with -r/--revision.
propset Sets the Subversion property given as the first argument, to the value given as the second argument for the file given as the third argument.
git svn propset svn:keywords "FreeBSD=%H" devel/py-tipper/Makefile
This will set the property svn:keywords to FreeBSD=%H for the file devel/py-tipper/Makefile.
show-externals Shows the Subversion externals. Use -r/--revision to specify a specific revision.
gc Compress $GIT_DIR/svn/<refname>/unhandled.log files and remove $GIT_DIR/svn/<refname>/index files.
reset Undoes the effects of fetch back to the specified revision. This allows you to re-fetch an SVN revision. Normally the contents of an SVN revision should never change and reset should not be necessary. However, if SVN permissions change, or if you alter your --ignore-paths option, a fetch may fail with "not found in commit" (file not previously visible) or "checksum mismatch" (missed a modification). If the problem file cannot be ignored forever (with --ignore-paths) the only way to repair the repo is to use reset.
Only the rev_map and refs/remotes/git-svn are changed (see $GIT_DIR/svn/**/.rev_map.*  in the FILES section below for details). Follow reset with a fetch and then git reset or git rebase to move local branches onto the new tree.
-r <n>, --revision=<n> Specify the most recent revision to keep. All later revisions are discarded.
-p, --parent Discard the specified revision as well, keeping the nearest parent instead.
Example: Assume you have local changes in "master", but you need to refetch "r2".
r1---r2---r3 remotes/git-svn \ A---B master
Fix the ignore-paths or SVN permissions problem that caused "r2" to be incomplete in the first place. Then:
git svn reset -r2 -p git svn fetch
r1---r2'--r3' remotes/git-svn \ r2---r3---A---B master
Then fixup "master" with git rebase. Do NOT use git merge or your history will not be compatible with a future dcommit!
git rebase --onto remotes/git-svn A^ master
r1---r2'--r3' remotes/git-svn \ A'--B' master
--shared[=(false|true|umask|group|all|world|everybody)], --template=<template_directory> Only used with the init command. These are passed directly to git init.
-r <arg>, --revision <arg> Used with the fetch command.
This allows revision ranges for partial/cauterized history to be supported. $NUMBER, $NUMBER1:$NUMBER2 (numeric ranges), $NUMBER:HEAD, and BASE:$NUMBER are all supported.
This can allow you to make partial mirrors when running fetch; but is generally not recommended because history will be skipped and lost.
-, --stdin Only used with the set-tree command.
Read a list of commits from stdin and commit them in reverse order. Only the leading sha1 is read from each line, so git rev-list --pretty=oneline output can be used.
--rmdir Only used with the dcommit, set-tree and commit-diff commands.
Remove directories from the SVN tree if there are no files left behind. SVN can version empty directories, and they are not removed by default if there are no files left in them. Git cannot version empty directories. Enabling this flag will make the commit to SVN act like Git.
config key: svn.rmdir
-e, --edit Only used with the dcommit, set-tree and commit-diff commands.
Edit the commit message before committing to SVN. This is off by default for objects that are commits, and forced on when committing tree objects.
config key: svn.edit
-l<num>, --find-copies-harder Only used with the dcommit, set-tree and commit-diff commands.
They are both passed directly to git diff-tree; see git-diff-tree(1) for more information.
config key: svn.l config key: svn.findcopiesharder
-A<filename>, --authors-file=<filename> Syntax is compatible with the file used by git cvsimport but an empty email address can be supplied with <>:
loginname = Joe User <user@example.com>
If this option is specified and git svn encounters an SVN committer name that does not exist in the authors-file, git svn will abort operation. The user will then have to add the appropriate entry. Re-running the previous git svn command after the authors-file is modified should continue operation.
config key: svn.authorsfile
--authors-prog=<filename> 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. The program is expected to return a single line of the form "Name <email>" or "Name <>", which will be treated as if included in the authors file.
Due to historical reasons a relative filename is first searched relative to the current directory for init and clone and relative to the root of the working tree for fetch. If filename is not found, it is searched like any other command in $PATH.
config key: svn.authorsProg
-q, --quiet Make git svn less verbose. Specify a second time to make it even less verbose.
-m, --merge, -s<strategy>, --strategy=<strategy>, -p, --rebase-merges These are only used with the dcommit and rebase commands.
Passed directly to git rebase when using dcommit if a git reset cannot be used (see dcommit).
-n, --dry-run This can be used with the dcommit, rebase, branch and tag commands.
For dcommit, print out the series of Git arguments that would show which diffs would be committed to SVN.
For rebase, display the local branch associated with the upstream svn repository associated with the current branch and the URL of svn repository that will be fetched from.
For branch and tag, display the urls that will be used for copying when creating the branch or tag.
--use-log-author When retrieving svn commits into Git (as part of fetch, rebase, or dcommit operations), look for the first From: line or Signed-off-by trailer in the log message and use that as the author string.
config key: svn.useLogAuthor
--add-author-from When committing to svn from Git (as part of set-tree or dcommit operations), if the existing log message doesn’t already have a From: or Signed-off-by trailer, append a From: line based on the Git commit’s author string. If you use this, then --use-log-author will retrieve a valid author string for all commits.
config key: svn.addAuthorFrom
-i<GIT_SVN_ID>, --id <GIT_SVN_ID> This sets GIT_SVN_ID (instead of using the environment). This allows the user to override the default refname to fetch from when tracking a single URL. The log and dcommit commands no longer require this switch as an argument.
-R<remote name>, --svn-remote <remote name> Specify the [svn-remote "<remote name>"] section to use, this allows SVN multiple repositories to be tracked. Default: "svn"
--follow-parent This option is only relevant if we are tracking branches (using one of the repository layout options --trunk, --tags, --branches, --stdlayout). For each tracked branch, try to find out where its revision was copied from, and set a suitable parent in the first Git commit for the branch. This is especially helpful when we’re tracking a directory that has been moved around within the repository. If this feature is disabled, the branches created by git svn will all be linear and not share any history, meaning that there will be no information on where branches were branched off or merged. However, following long/convoluted histories can take a long time, so disabling this feature may speed up the cloning process. This feature is enabled by default, use --no-follow-parent to disable it.
config key: svn.followparent
CONFIG FILE-ONLY OPTIONS svn.noMetadata, svn-remote.<name>.noMetadata This gets rid of the git-svn-id: lines at the end of every commit.
This option can only be used for one-shot imports as git svn will not be able to fetch again without metadata. Additionally, if you lose your $GIT_DIR/svn/**/.rev_map.*  files, git svn will not be able to rebuild them.
The git svn log command will not work on repositories using this, either. Using this conflicts with the useSvmProps option for (hopefully) obvious reasons.
This option is NOT recommended as it makes it difficult to track down old references to SVN revision numbers in existing documentation, bug reports, and archives. If you plan to eventually migrate from SVN to Git and are certain about dropping SVN history, consider git-filter-repo[1] instead. filter-repo also allows reformatting of metadata for ease-of-reading and rewriting authorship info for non-"svn.authorsFile" users.
svn.useSvmProps, svn-remote.<name>.useSvmProps This allows git svn to re-map repository URLs and UUIDs from mirrors created using SVN::Mirror (or svk) for metadata.
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. We want to make it look like we are mirroring the original URL, so introduce a helper function that returns the original identity URL and UUID, and use it when generating metadata in commit messages.
svn.useSvnsyncProps, svn-remote.<name>.useSvnsyncprops Similar to the useSvmProps option; this is for users of the svnsync(1) command distributed with SVN 1.4.x and later.
svn-remote.<name>.rewriteRoot This allows users to create repositories from alternate URLs. For example, an administrator could run git svn on the server locally (accessing via file://) but wish to distribute the repository with a public http:// or svn:// URL in the metadata so users of it will see the public URL.
svn-remote.<name>.rewriteUUID Similar to the useSvmProps option; this is for users who need to remap the UUID manually. This may be useful in situations where the original UUID is not available via either useSvmProps or useSvnsyncProps.
svn-remote.<name>.pushurl Similar to Git’s remote.<name>.pushurl, this key is designed to be used in cases where url points to an SVN repository via a read-only transport, to provide an alternate read/write transport. It is assumed that both keys point to the same repository. Unlike commiturl, pushurl is a base path. If either commiturl or pushurl could be used, commiturl takes precedence.
svn.brokenSymlinkWorkaround This disables potentially expensive checks to workaround broken symlinks checked into SVN by broken clients. Set this option to "false" if you track a SVN repository with many empty blobs that are not symlinks. This option may be changed while git svn is running and take effect on the next revision fetched. If unset, git svn assumes this option to be "true".
svn.pathnameencoding This instructs git svn to recode pathnames to a given encoding. It can be used by windows users and by those who work in non-utf8 locales to avoid corrupted file names with non-ASCII characters. Valid encodings are the ones supported by Perl’s Encode module.
svn-remote.<name>.automkdirs Normally, the "git svn clone" and "git svn rebase" commands attempt to recreate empty directories that are in the Subversion repository. If this option is set to "false", then empty directories will only be created if the "git svn mkdirs" command is run explicitly. If unset, git svn assumes this option to be "true".
Since the noMetadata, rewriteRoot, rewriteUUID, useSvnsyncProps and useSvmProps options all affect the metadata generated and used by git svn; they must be set in the configuration file before any history is imported and these settings should never be changed once they are set.
Additionally, only one of these options can be used per svn-remote section because they affect the git-svn-id: metadata line, except for rewriteRoot and rewriteUUID which can be used together.
Tracking and contributing to the trunk of a Subversion-managed project (ignoring tags and branches):
# Clone a repo (like git clone): git svn clone http://svn.example.com/project/trunk # Enter the newly cloned directory: cd trunk # You should be on master branch, double-check with 'git branch' git branch # Do some work and commit locally to Git: git commit ... # Something is committed to SVN, rebase your local changes against the # latest changes in SVN: git svn rebase # Now commit your changes (that were committed previously using Git) to SVN, # as well as automatically updating your working HEAD: git svn dcommit # Append svn:ignore settings to the default Git exclude file: git svn show-ignore >> .git/info/exclude
Tracking and contributing to an entire Subversion-managed project (complete with a trunk, tags and branches):
# Clone a repo with standard SVN directory layout (like git clone): git svn clone http://svn.example.com/project --stdlayout --prefix svn/ # Or, if the repo uses a non-standard directory layout: git svn clone http://svn.example.com/project -T tr -b branch -t tag --prefix svn/ # View all branches and tags you have cloned: git branch -r # Create a new branch in SVN git svn branch waldo # Reset your master to trunk (or any other branch, replacing 'trunk' # with the appropriate name): git reset --hard svn/trunk # You may only dcommit to one branch/tag/trunk at a time.  The usage # of dcommit/rebase/show-ignore should be the same as above.
The initial git svn clone can be quite time-consuming (especially for large Subversion repositories). If multiple people (or one person with multiple machines) want to use git svn to interact with the same Subversion repository, you can do the initial git svn clone to a repository on a server and have each person clone that repository with git clone:
# Do the initial import on a server ssh server "cd /pub && git svn clone http://svn.example.com/project [options...]" # Clone locally - make sure the refs/remotes/ space matches the server mkdir project cd project git init git remote add origin server:/pub/project git config --replace-all remote.origin.fetch '+refs/remotes/*:refs/remotes/*' git fetch # Prevent fetch/pull from remote Git server in the future, # we only want to use git svn for future updates git config --remove-section remote.origin # Create a local branch from one of the branches just fetched git checkout -b master FETCH_HEAD # Initialize 'git svn' locally (be sure to use the same URL and # --stdlayout/-T/-b/-t/--prefix options as were used on server) git svn init http://svn.example.com/project [options...] # Pull the latest changes from Subversion git svn rebase
REBASE VS. PULL/MERGE Prefer to use git svn rebase or git rebase, rather than git pull or git merge to synchronize unintegrated commits with a git svn branch. Doing so will keep the history of unintegrated commits linear with respect to the upstream SVN repository and allow the use of the preferred git svn dcommit subcommand to push unintegrated commits back into SVN.
Originally, git svn recommended that developers pulled or merged from the git svn branch. This was because the author favored git svn set-tree B to commit a single head rather than the git svn set-tree A..B notation to commit multiple commits. Use of git pull or git merge with git svn set-tree A..B will cause non-linear history to be flattened when committing into SVN and this can lead to merge commits unexpectedly reversing previous commits in SVN.
While git svn can track copy history (including branches and tags) for repositories adopting a standard layout, it cannot yet represent merge history that happened inside git back upstream to SVN users. Therefore it is advised that users keep history as linear as possible inside Git to ease compatibility with SVN (see the CAVEATS section below).
If git svn is configured to fetch branches (and --follow-branches is in effect), it sometimes creates multiple Git branches for one SVN branch, where the additional branches have names of the form branchname@nnn (with nnn an SVN revision number). These additional branches are created if git svn cannot find a parent commit for the first commit in an SVN branch, to connect the branch to the history of the other branches.
Normally, the first commit in an SVN branch consists of a copy operation. git svn will read this commit to get the SVN revision the branch was created from. It will then try to find the Git commit that corresponds to this SVN revision, and use that as the parent of the branch. However, it is possible that there is no suitable Git commit to serve as parent. This will happen, among other reasons, if the SVN branch is a copy of a revision that was not fetched by git svn (e.g. because it is an old revision that was skipped with --revision), or if in SVN a directory was copied that is not tracked by git svn (such as a branch that is not tracked at all, or a subdirectory of a tracked branch). In these cases, git svn will still create a Git branch, but instead of using an existing Git commit as the parent of the branch, it will read the SVN history of the directory the branch was copied from and create appropriate Git commits. This is indicated by the message "Initializing parent: <branchname>".
Additionally, it will create a special branch named <branchname>@<SVN-Revision>, where <SVN-Revision> is the SVN revision number the branch was copied from. This branch will point to the newly created parent commit of the branch. If in SVN the branch was deleted and later recreated from a different version, there will be multiple such branches with an @.
Note that this may mean that multiple Git commits are created for a single SVN revision.
An example: in an SVN repository with a standard trunk/tags/branches layout, a directory trunk/sub is created in r.100. In r.200, trunk/sub is branched by copying it to branches/. git svn clone -s will then create a branch sub. It will also create new Git commits for r.100 through r.199 and use these as the history of branch sub. Thus there will be two Git commits for each revision from r.100 to r.199 (one containing trunk/, one containing trunk/sub/). Finally, it will create a branch sub@200 pointing to the new parent commit of branch sub (i.e. the commit for r.200 and trunk/sub/).
For the sake of simplicity and interoperating with Subversion, it is recommended that all git svn users clone, fetch and dcommit directly from the SVN server, and avoid all git clone/pull/merge/push operations between Git repositories and branches. The recommended method of exchanging code between Git branches and users is git format-patch and git am, or just 'dcommit’ing to the SVN repository.
Running git merge or git pull is NOT recommended on a branch you plan to dcommit from because Subversion users cannot see any merges you’ve made. Furthermore, if you merge or pull from a Git branch that is a mirror of an SVN branch, dcommit may commit to the wrong branch.
If you do merge, note the following rule: git svn dcommit will attempt to commit on top of the SVN commit named in
git log --grep=^git-svn-id: --first-parent -1
You must therefore ensure that the most recent commit of the branch you want to dcommit to is the first parent of the merge. Chaos will ensue otherwise, especially if the first parent is an older commit on the same SVN branch.
git clone does not clone branches under the refs/remotes/ hierarchy or any git svn metadata, or config. So repositories created and managed with using git svn should use rsync for cloning, if cloning is to be done at all.
Since dcommit uses rebase internally, any Git branches you git push to before dcommit on will require forcing an overwrite of the existing ref on the remote repository. This is generally considered bad practice, see the git-push(1) documentation for details.
Do not use the --amend option of git-commit(1) on a change you’ve already dcommitted. It is considered bad practice to --amend commits you’ve already pushed to a remote repository for other users, and dcommit with SVN is analogous to that.
When cloning an SVN repository, if none of the options for describing the repository layout is used (--trunk, --tags, --branches, --stdlayout), git svn clone will create a Git repository with completely linear history, where branches and tags appear as separate directories in the working copy. While this is the easiest way to get a copy of a complete repository, for projects with many branches it will lead to a working copy many times larger than just the trunk. Thus for projects using the standard directory structure (trunk/branches/tags), it is recommended to clone with option --stdlayout. If the project uses a non-standard structure, and/or if branches and tags are not required, it is easiest to only clone one directory (typically trunk), without giving any repository layout options. If the full history with branches and tags is required, the options --trunk / --branches / --tags must be used.
When using multiple --branches or --tags, git svn does not automatically handle name collisions (for example, if two branches from different paths have the same name, or if a branch and a tag have the same name). In these cases, use init to set up your Git repository then, before your first fetch, edit the $GIT_DIR/config file so that the branches and tags are associated with different name spaces. For example:
branches = stable/*:refs/remotes/svn/stable/* branches = debug/*:refs/remotes/svn/debug/*
git svn stores [svn-remote] configuration information in the repository $GIT_DIR/config file. It is similar the core Git [remote] sections except fetch keys do not accept glob arguments; but they are instead handled by the branches and tags keys. Since some SVN repositories are oddly configured with multiple projects glob expansions such those listed below are allowed:
[svn-remote "project-a"] url = http://server.org/svn fetch = trunk/project-a:refs/remotes/project-a/trunk branches = branches/*/project-a:refs/remotes/project-a/branches/* branches = branches/release_*:refs/remotes/project-a/branches/release_* branches = branches/re*se:refs/remotes/project-a/branches/* tags = tags/*/project-a:refs/remotes/project-a/tags/*
Keep in mind that the * (asterisk) wildcard of the local ref (right of the :) must be the farthest right path component; however the remote wildcard may be anywhere as long as it’s an independent path component (surrounded by / or EOL). This type of configuration is not automatically created by init and should be manually entered with a text-editor or using git config.
Also note that only one asterisk is allowed per word. For example:
branches = branches/re*se:refs/remotes/project-a/branches/*
will match branches release, rese, re123se, however
branches = branches/re*s*e:refs/remotes/project-a/branches/*
will produce an error.
It is also possible to fetch a subset of branches or tags by using a comma-separated list of names within braces. For example:
[svn-remote "huge-project"] url = http://server.org/svn fetch = trunk/src:refs/remotes/trunk branches = branches/{red,green}/src:refs/remotes/project-a/branches/* tags = tags/{1.0,2.0}/src:refs/remotes/project-a/tags/*
Multiple fetch, branches, and tags keys are supported:
[svn-remote "messy-repo"] url = http://server.org/svn fetch = trunk/project-a:refs/remotes/project-a/trunk fetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo branches = branches/server/*:refs/remotes/project-a/branches/* branches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/* tags = tags/server/*:refs/remotes/project-a/tags/*
Creating a branch in such a configuration requires disambiguating which location to use using the -d or --destination flag:
$ git svn branch -d branches/server release-2-3-0
Note that git-svn keeps track of the highest revision in which a branch or tag has appeared. If the subset of branches or tags is changed after fetching, then $GIT_DIR/svn/.metadata must be manually edited to remove (or reset) branches-maxRev and/or tags-maxRev as appropriate.
$GIT_DIR/svn/**/.rev_map.* Mapping between Subversion revision numbers and Git commit names. In a repository where the noMetadata option is not set, this can be rebuilt from the git-svn-id: lines that are at the end of every commit (see the svn.noMetadata section above for details).
git svn fetch and git svn rebase automatically update the rev_map if it is missing or not up to date.  git svn reset automatically rewinds it.
We ignore all SVN properties except svn:executable. Any unhandled properties are logged to $GIT_DIR/svn/<refname>/unhandled.log
Renamed and copied directories are not detected by Git and hence not tracked when committing to SVN. I do not plan on adding support for this as it’s quite difficult and time-consuming to get working for all the possible corner cases (Git doesn’t do it, either). Committing renamed and copied files is fully supported if they’re similar enough for Git to detect them.
In SVN, it is possible (though discouraged) to commit changes to a tag (because a tag is just a directory copy, thus technically the same as a branch). When cloning an SVN repository, git svn cannot know if such a commit to a tag will happen in the future. Thus it acts conservatively and imports all SVN tags as branches, prefixing the tag name with tags/.
git-rebase(1)
SFILL(1)                     General Commands Manual                    SFILL(1)
sfill - secure free disk and inode space wiper (secure_deletion toolkit)
sfill [-f] [-i] [-I] [-l] [-l] [-v] [-z] directory/mountpoint
sfill is designed to delete data which lies on available diskspace on mediums in a secure manner which can not be recovered by thieves, law enforcement or other threats.  The wipe algorithm is based on the paper "Secure Deletion of Data from Magnetic and Solid-State Memory" presented at the 6th Usenix Security Symposium by Peter Gutmann, one of the leading civilian cryptographers.
The secure data deletion process of sfill goes like this:
*      1 pass with 0xff
*      5 random passes. /dev/urandom is used for a secure RNG if available.
*      27 passes with special values defined by Peter Gutmann.
afterwards as many temporary files as possible are generated to wipe the free inode space. After no more temporary files can be created, they are removed and sfill is finished.
-f     fast (and insecure mode): no /dev/urandom, no synchronize mode.
-i     wipe only free inode space, not free disk space
-I     wipe only free disk space, not free inode space
-l     lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.
-l     -l for a second time lessons the security even more: only one random pass is written.
-v     verbose mode
-z     wipes the last write with zeros instead of random data
directory/mountpoint this is the location of the file created in your filesystem. It should lie on the partition you want to write.
FILESYSTEM INTELLIGENCE Most filesystems (ext2, ffs, etc.) have several features included to enhance performance, which will result in that sfill might not receive all available free space. Sad but true. Nothing can be done about that ...
NFS    Beware of NFS. You can't ensure you really completely wiped your data from the remote disks. (especially because of caching)
Raid   Raid Systems use stripped disks and have got large caches. It's hard to wipe them.
swap   Some of your data might have a copy in your swapspace.  sswap is available for this task.
No bugs. There was never a bug in the secure_deletion package (in contrast to my other tools, whew, good luck ;-) Send me any that you find.  Patches are nice too :)
van Hauser / THC <vh@thc.org>
The newest version of the secure_deletion package can be obtained from http://www.thc.org
sfill and the secure_deletion package is (C) 1997-2003 by van Hauser / THC (vh@thc.org)
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; Version 2.
srm (1), sswap (1), sdmem (1)
XMLTO(1)                            Reference                           XMLTO(1)
xmlto - apply an XSL stylesheet to an XML document
xmlto [-o output_dir] [-x custom_xsl] [-m xsl_fragment] [-v] [-p postprocessor_opts] [--extensions] [--searchpath path] [--skip-validation] [--stringparam paramname=paramvalue] [--noclean] [--noautosize] [--noextensions] [--profile] [--with-fop] [--with-dblatex] {format} {file}
xmlto {[--help] | [--version]}
The purpose of xmlto is to convert an XML file to the desired format using whatever means necessary. This may involve two steps:
1. The application of an appropriate XSL stylesheet using an XSL-T processor.
2. Further processing with other tools. This step may not be necessary.
To decide which stylesheet to use and what, if any, needs to be done to post-process the output, xmlto makes use of format scripts, which are simple shell scripts that xmlto calls during the conversion.
The appropriate format script is selected based on the type of XML file and the desired output format.  xmlto comes with some format scripts for converting DocBook XML files to a variety of formats. You may specify your own format script by using an absolute filename for format on the command line.
Firstly, if xmlto has not been told explicitly which stylesheet to use (with the -x option), the format script will be called with $1 set to stylesheet. The environment variable XSLT_PROCESSOR contains the base name of the executable that will be used to perform the XSL-T transformation (for example xsltproc). The format script should write the name of the stylesheet to use to standard output and exit successfully, or exit with a non-zero return code if there is no appropriate stylesheet to use (for example, if the only available stylesheet is known not to work with the XSL-T processor that will be used). If nothing is written to standard output but the script exits successfully, no XSL-T transformation will be performed.
Secondly, after an XSL-T processor has been run using the stylesheet, the format script will be called again, this time with $1 set to post-process. The format script should perform any necessary steps to translate the XSL-T processed output into the desired output format, including copying the output to the desired output directory. For post-processing, the format script is run in a temporary directory containing just the processed output (whose name is stored in XSLT_PROCESSED and whose basename is that of the original XML file with any filename extension replaced with .proc).  INPUT_FILE is set to the name of the original XML file, OUTPUT_DIR is set to the name of the directory that the output (and only the output) must end up in, and SEARCHPATH is set to a colon-separate list of fallback directories in which to look for input (for images, for example). If this step is unsuccessful the format script should exit with a non-zero return code.
-v Be verbose (-vv for very verbose).
-x stylesheet Use stylesheet instead of asking the format script to choose one.
-m fragment Use the provided XSL fragment to modify the stylesheet.
-o directory Put output in the specified directory instead of the current working directory.
-p postprocessor_opts Pass postprocessor_opts to processing stages after stylesheet application (e.g.  lynx or links when going through HTML to text, or xmltex when going from through TeX to DVI). If -p is specified a second time, the options specified will be passed to second-stage postprocessing; presently this is only applicable when going through xmltex and dvips to PostScript.
--extensions Turn on stylesheet extensions for the tool chain in use (use.extensions is turned on). The variables turned on are the ones used by Norman Walsh's DocBook XSL stylesheets.
--searchpath path Add the colon-separated list of directories in path as fallback directories for including input.
--skip-validation Skip the validation step that is normally performed.
--stringparam paramname=paramvalue Pass a named parameter paramname with value paramvalue to stylesheet from the command line.
--noclean Temporary files are not deleted(their names are shown and kept in tmp directory). It could help with analyzing problems.
--noautosize By default, some XSL variables are overridden by autodetection (page.width and page.height for paperconf (libpaper) use, paper.type for locale-based (LC_PAPER) selection). With this option, xmlto doesn’t use this autodetection and user is able to modify defaults himself (either via default param.xsl modification or by user-defined XSL fragment).
--noextensions By default, xmlto enables XSL params passivetex.extensions for passivetex backend and fop.extensions and fop1.extensions for fop backend. This usually produces better results. If you for some reason don't want to use these parameters, just disable them using this option.
--profile Pre-process the XML document with the profiling stylesheet.
--with-fop Use fop for formatting. It is an experimental option, expects fop in specific location(detected at configured time), could be changed manually in xmlto script by modification of FOP_PATH
--with-dblatex Use dblatex for formatting. It is an experimental option, expects dblatex in specific location(detected at configured time), could be changed manually in xmlto script by modification of DBLATEX_PATH
--help Display a short usage message. It will describe xmlto's options, and the available output formats.
--version Display the version number of xmlto.
XSLT_PROCESSOR Base name of the executable that will be used to perform the XSL-T transformation (default: xsltproc(1)).
TMPDIR Directory, where to create temporary stylesheets (default: /tmp).
0 Everything went fine. This is the expected exit code.
1 xmlto was called with insufficient arguments.
2 mktemp(1) failed to create a file/directory. Make sure /tmp or TMPDIR is writable.
3 xmlto failed to find some binary on configured location. Make sure that all required packages are installed and paths in xmlto script are set properly.
10+(Validation non-zero error code) xmlto tried to validate a xml document, but validation failed. For better diagnostic, validation output and xmllint exit code is provided. Consider either fixing your document or using --skip-validation.
To convert a DocBook XML document to PDF, use:
xmlto pdf mydoc.xml
To convert a DocBook XML document to HTML and store the resulting HTML files in a separate directory use:
xmlto -o html-dir html mydoc.xml
To convert a DocBook XML document to a single HTML file use:
xmlto html-nochunks mydoc.xml
To modify the output using an XSL fragment use:
xmlto -m ulink.xsl pdf mydoc.xml
To specify which stylesheet to use (overriding the one that the format script would choose) use:
xmlto -x mystylesheet.xsl pdf mydoc.xml
Tim Waugh <twaugh@redhat.com> Original author, maintainer until 0.0.18
Ondřej Vašík <ovasik@redhat.com> Maintainer since 0.0.19
NEEDRESTART(1)                    User Commands                   NEEDRESTART(1)
needrestart - needrestart
needrestart checks which daemons need to be restarted after library upgrades.
needrestart [-(v|q)] [-n] [-c <cfg>] [-r <mode>] [-f <fe>] [-u <ui>] [-(b|p)] [-kl]
-v     be more verbose
-q     be quiet
-m <mode> set level of technical details
e   (e)asy mode
a   (a)dvanced mode
-n     set default answer to 'no'
-c <cfg> config filename
-r <mode> set restart mode
l   (l)ist only
i   (i)nteractive restart
a   (a)utomatically restart
ATTENTION: If needrestart is configured to run in interactive mode but is run non-interactive (i.e. unattended-upgrades) it will fallback to list only mode.
-b     enable batch mode
-p     nagios plugin mode: makes output and exit codes nagios compatible
-f <fe> overwrite debconf(7) frontend, sets the DEBIAN_FRONTEND environment variable to <fe>
-u <ui> use preferred UI package (-u ? shows available packages)
By using one of the following options only the specified checks are performed:
-k     check for obsolete kernel
-l     check for obsolete libraries
The following environment variables can be used to override the config file options. Command line parameters do always supersede them.
NEEDRESTART_MODE Change the configured restart mode (see also the -r parameter): (l)ist only, (i)nteractive or (a)utomatically
When used with apt-get(8) needrestart supports the following additional environment variables:
DEBIAN_FRONT The debconf(7) frontend to use, can also set using the -f parameter.
NEEDRESTART_SUSPEND If set to a non-empty value the apt-get(8) hook will not run needrestart after installing or updating packages.
Thomas Liske <thomas@fiasko-nw.net>
2013 - 2018 (C) Thomas Liske [http://fiasko-nw.net/~thomas/]
https://github.com/liske/needrestart
SALT-RUN(1)                           Salt                           SALT-RUN(1)
salt-run - salt-run Documentation
Execute a Salt runner
salt-run RUNNER
salt-run is the frontend command for executing Salt Runners.  Salt runners are simple modules used to execute convenience functions on the master
salt(1) salt-master(1) salt-minion(1)
Xephyr(1)                    General Commands Manual                   Xephyr(1)
Xephyr - X server outputting to a window on a pre-existing X display
Xephyr [:display] [option ...]
Xephyr is a kdrive server that outputs to a window on a pre-existing "host" X display.  Think Xnest but with support for modern extensions like composite, damage and randr.
Unlike Xnest which is an X proxy, i.e.  limited to the capabilities of the host X server, Xephyr is a real X server which uses the host X server window as "framebuffer" via fast SHM XImages.
It also has support for "visually" debugging what the server is painting.
The server accepts all the standard options of Xserver(1) and the following additional options:
-screen widthxheight sets the screen size.
-parent id uses existing window id .  If a -screen argument follows a -parent argument, this screen is embedded into the given window.
-host-cursor set 'cursor acceleration': The host's cursor is reused. This is only really there to aid debugging by avoiding server paints for the cursor. Performance improvement is negligible.
-resizeable Allow the Xephyr window to be resized, even if not embedded into a parent window. By default, the Xephyr window has a fixed size.
-no-host-grab Disable grabbing the keyboard and mouse.
Send a SIGUSR1 to the server (e.g. pkill -USR1 Xephyr) to toggle the debugging mode.  In this mode red rectangles are painted to screen areas getting painted before painting the actual content.  The delay between this can be altered by setting a XEPHYR_PAUSE env var to a value in micro seconds.
• Rotated displays are currently updated via full blits. This is slower than a normal orientated display. Debug mode will therefore not be of much use rotated.
• The '-host-cursor' cursor is static in its appearance.
• The build gets a warning about 'nanosleep'. I think the various '-D' build flags are causing this. I haven't figured as yet how to work round it. It doesn't appear to break anything however.
• Keyboard handling is basic but works.
• Mouse button 5 probably won't work.
X(7), Xserver(1)
Matthew Allum <mallum@o-hand.com> 2004
IONICE(1)                         User Commands                        IONICE(1)
ionice - set or get process I/O scheduling class and priority
ionice [-c class] [-n level] [-t] -p PID
ionice [-c class] [-n level] [-t] -P PGID
ionice [-c class] [-n level] [-t] -u UID
ionice [-c class] [-n level] [-t] command [argument] ...
This program sets or gets the I/O scheduling class and priority for a program. If no arguments or just -p is given, ionice will query the current I/O scheduling class and priority for that process.
When command is given, ionice will run this command with the given arguments. If no class is specified, then command will be executed with the "best-effort" scheduling class. The default priority level is 4.
As of this writing, a process can be in one of three scheduling classes:
Idle A program running with idle I/O priority will only get disk time when no other program has asked for disk I/O for a defined grace period. The impact of an idle I/O process on normal system activity should be zero. This scheduling class does not take a priority argument. Presently, this scheduling class is permitted for an ordinary user (since kernel 2.6.25).
Best-effort This is the effective scheduling class for any process that has not asked for a specific I/O priority. This class takes a priority argument from 0-7, with a lower number being higher priority. Programs running at the same best-effort priority are served in a round-robin fashion.
Note that before kernel 2.6.26 a process that has not asked for an I/O priority formally uses "none" as scheduling class, but the I/O scheduler will treat such processes as if it were in the best-effort class. The priority within the best-effort class will be dynamically derived from the CPU nice level of the process: io_priority = (cpu_nice + 20) / 5.
For kernels after 2.6.26 with the CFQ I/O scheduler, a process that has not asked for an I/O priority inherits its CPU scheduling class. The I/O priority is derived from the CPU nice level of the process (same as before kernel 2.6.26).
Realtime The RT scheduling class is given first access to the disk, regardless of what else is going on in the system. Thus the RT class needs to be used with some care, as it can starve other processes. As with the best-effort class, 8 priority levels are defined denoting how big a time slice a given process will receive on each scheduling window. This scheduling class is not permitted for an ordinary (i.e., non-root) user.
-c, --class class Specify the name or number of the scheduling class to use; 0 for none, 1 for realtime, 2 for best-effort, 3 for idle.
-n, --classdata level Specify the scheduling class data. This only has an effect if the class accepts an argument. For realtime and best-effort, 0-7 are valid data (priority levels), and 0 represents the highest priority level.
-p, --pid PID... Specify the process IDs of running processes for which to get or set the scheduling parameters.
-P, --pgid PGID... Specify the process group IDs of running processes for which to get or set the scheduling parameters.
-t, --ignore Ignore failure to set the requested priority. If command was specified, run it even in case it was not possible to set the desired scheduling priority, which can happen due to insufficient privileges or an old kernel version.
-u, --uid UID... Specify the user IDs of running processes for which to get or set the scheduling parameters.
Linux supports I/O scheduling priorities and classes since 2.6.13 with the CFQ I/O scheduler.
•   # ionice -c 3 -p 89
Sets process with PID 89 as an idle I/O process.
•   # ionice -c 2 -n 0 bash
Runs 'bash' as a best-effort program with highest priority.
•   # ionice -p 89 91
Prints the class and priority of the processes with PID 89 and 91.
Jens Axboe <jens@axboe.dk>, Karel Zak <kzak@redhat.com>
ioprio_set(2)
The ionice command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
PACMAN4CONSOLE(6)           Console based pacman game          PACMAN4CONSOLE(6)
pacman4console - console based pacman game
pacman4console [ OPTION ]
This manual page documents briefly the pacman4console.
pacman4console is an ASCII character based game. This game has nine levels officially.
-h, --help print help
--level=[1..9] start at specified standard level
--level=LEVEL play specified non-standard LEVEL
pacman4consoleedit(1)