{"thread":{"id":"25883","subject":"[PATCH] git-rm.txt: Order options alphabetically","startedAt":"2010-12-01T15:44:50Z","lastAt":"2010-12-01T15:44:50Z","messageCount":1,"participants":["jari.aalto@cante.net"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"156946","messageId":"1291218290-13159-1-git-send-email-jari.aalto@cante.net","threadId":"25883","inReplyTo":null,"subject":"[PATCH] git-rm.txt: Order options alphabetically","fromName":"","fromEmail":"jari.aalto@cante.net","sentAt":"2010-12-01T15:44:50Z","receivedAt":"2010-12-01T15:44:50Z","isPatch":true,"sender":{"key":"jari.aalto@cante.net","avatar":"https://avatars.githubusercontent.com/u/34601?v=4"},"body":"From: Jari Aalto <jari.aalto@cante.net>\n\n\nSigned-off-by: Jari Aalto <jari.aalto@cante.net>\n---\n Documentation/git-rm.txt |   44 +++++++++++++++++++++-----------------------\n 1 files changed, 21 insertions(+), 23 deletions(-)\n\ndiff --git a/Documentation/git-rm.txt b/Documentation/git-rm.txt\nindex 71e3d9f..5478e0c 100644\n--- a/Documentation/git-rm.txt\n+++ b/Documentation/git-rm.txt\n@@ -22,29 +22,31 @@ When `--cached` is given, the staged content has to\n match either the tip of the branch or the file on disk,\n allowing the file to be removed from just the index.\n \n-\n OPTIONS\n -------\n-<file>...::\n-\tFiles to remove.  Fileglobs (e.g. `*.c`) can be given to\n-\tremove all matching files.  If you want git to expand\n-\tfile glob characters, you may need to shell-escape them.\n-\tA leading directory name\n-\t(e.g. `dir` to remove `dir/file1` and `dir/file2`) can be\n-\tgiven to remove all files in the directory, and recursively\n-\tall sub-directories,\n-\tbut this requires the `-r` option to be explicitly given.\n+\n+--cached::\n+\tUse this option to unstage and remove paths only from the index.\n+\tWorking tree files, whether modified or not, will be\n+\tleft alone.\n \n -f::\n --force::\n \tOverride the up-to-date check.\n \n+--ignore-unmatch::\n+\tExit with a zero status even if no files matched.\n+\n -n::\n --dry-run::\n \tDon't actually remove any file(s).  Instead, just show\n \tif they exist in the index and would otherwise be removed\n \tby the command.\n \n+-q::\n+--quiet::\n+\t`git rm` normally outputs one line (in the form of an `rm` command)\n+\tfor each file removed. This option suppresses that output.\n -r::\n         Allow recursive removal when a leading directory name is\n         given.\n@@ -54,19 +56,15 @@ OPTIONS\n \tthe list of files, (useful when filenames might be mistaken\n \tfor command-line options).\n \n---cached::\n-\tUse this option to unstage and remove paths only from the index.\n-\tWorking tree files, whether modified or not, will be\n-\tleft alone.\n-\n---ignore-unmatch::\n-\tExit with a zero status even if no files matched.\n-\n--q::\n---quiet::\n-\t`git rm` normally outputs one line (in the form of an `rm` command)\n-\tfor each file removed. This option suppresses that output.\n-\n+<file>...::\n+\tFiles to remove.  Fileglobs (e.g. `*.c`) can be given to\n+\tremove all matching files.  If you want git to expand\n+\tfile glob characters, you may need to shell-escape them.\n+\tA leading directory name\n+\t(e.g. `dir` to remove `dir/file1` and `dir/file2`) can be\n+\tgiven to remove all files in the directory, and recursively\n+\tall sub-directories,\n+\tbut this requires the `-r` option to be explicitly given.\n \n DISCUSSION\n ----------\n-- \n1.7.2.3\n"}]}