{"thread":{"id":"25906","subject":"[PATCH] git-clone.txt: order options alphabetically","startedAt":"2010-12-01T20:09:32Z","lastAt":"2010-12-01T20:09:32Z","messageCount":1,"participants":["jari.aalto@cante.net"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"157006","messageId":"1291234172-20927-1-git-send-email-jari.aalto@cante.net","threadId":"25906","inReplyTo":null,"subject":"[PATCH] git-clone.txt: order options alphabetically","fromName":"","fromEmail":"jari.aalto@cante.net","sentAt":"2010-12-01T20:09:32Z","receivedAt":"2010-12-01T20:09:32Z","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-clone.txt |  173 ++++++++++++++++++++++---------------------\n 1 files changed, 87 insertions(+), 86 deletions(-)\n\ndiff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt\nindex 42e7021..35f5017 100644\n--- a/Documentation/git-clone.txt\n+++ b/Documentation/git-clone.txt\n@@ -37,8 +37,37 @@ configuration variables.\n \n OPTIONS\n -------\n---local::\n+\n+--bare::\n+\tMake a 'bare' GIT repository.  That is, instead of\n+\tcreating `<directory>` and placing the administrative\n+\tfiles in `<directory>/.git`, make the `<directory>`\n+\titself the `$GIT_DIR`. This obviously implies the `-n`\n+\tbecause there is nowhere to check out the working tree.\n+\tAlso the branch heads at the remote are copied directly\n+\tto corresponding local branch heads, without mapping\n+\tthem to `refs/remotes/origin/`.  When this option is\n+\tused, neither remote-tracking branches nor the related\n+\tconfiguration variables are created.\n+\n+-b <name>::\n+--branch <name>::\n+\tInstead of pointing the newly created HEAD to the branch pointed\n+\tto by the cloned repository's HEAD, point to `<name>` branch\n+\tinstead. In a non-bare repository, this is the branch that will\n+\tbe checked out.\n+\n+--depth <depth>::\n+\tCreate a 'shallow' clone with a history truncated to the\n+\tspecified number of revisions.  A shallow repository has a\n+\tnumber of limitations (you cannot clone or fetch from\n+\tit, nor push from nor into it), but is adequate if you\n+\tare only interested in the recent history of a large project\n+\twith a long history, and would want to send in fixes\n+\tas patches.\n+\n -l::\n+--local::\n \tWhen the repository to clone from is on a local machine,\n \tthis flag bypasses the normal \"git aware\" transport\n \tmechanism and clones the repository by making a copy of\n@@ -52,13 +81,61 @@ OPTIONS\n \tbut still avoid the usual \"git aware\" transport\n \tmechanism, `--no-hardlinks` can be used.\n \n+--mirror::\n+\tSet up a mirror of the source repository.  This implies `--bare`.\n+\tCompared to `--bare`, `--mirror` not only maps local branches of the\n+\tsource to local branches of the target, it maps all refs (including\n+\tremote-tracking branches, notes etc.) and sets up a refspec configuration such\n+\tthat all these refs are overwritten by a `git remote update` in the\n+\ttarget repository.\n+\n+-n::\n+--no-checkout::\n+\tNo checkout of HEAD is performed after the clone is complete.\n+\n --no-hardlinks::\n \tOptimize the cloning process from a repository on a\n \tlocal filesystem by copying files under `.git/objects`\n \tdirectory.\n \n---shared::\n+-o <name>::\n+--origin <name>::\n+\tInstead of using the remote name `origin` to keep track\n+\tof the upstream repository, use `<name>`.\n+\n+--progress::\n+\tProgress status is reported on the standard error stream\n+\tby default when it is attached to a terminal, unless -q\n+\tis specified. This flag forces progress status even if the\n+\tstandard error stream is not directed to a terminal.\n+\n+-q::\n+--quiet::\n+\tOperate quietly.  Progress is not reported to the standard\n+\terror stream. This flag is also passed to the `rsync'\n+\tcommand when given.\n+\n+--recursive::\n+--recurse-submodules::\n+\tAfter the clone is created, initialize all submodules within,\n+\tusing their default settings. This is equivalent to running\n+\t`git submodule update --init --recursive` immediately after\n+\tthe clone is finished. This option is ignored if the cloned\n+\trepository does not have a worktree/checkout (i.e. if any of\n+\t`--no-checkout`/`-n`, `--bare`, or `--mirror` is given)\n+\n+--reference <repository>::\n+\tIf the reference repository is on the local machine,\n+\tautomatically setup `.git/objects/info/alternates` to\n+\tobtain objects from the reference repository.  Using\n+\tan already existing repository as an alternate will\n+\trequire fewer objects to be copied from the repository\n+\tbeing cloned, reducing network and local storage costs.\n++\n+*NOTE*: see the NOTE for the `--shared` option.\n+\n -s::\n+--shared::\n \tWhen the repository to clone is on the local machine,\n \tinstead of using hard links, automatically setup\n \t`.git/objects/info/alternates` to share the objects\n@@ -85,96 +162,20 @@ If you want to break the dependency of a repository cloned with `-s` on\n its source repository, you can simply run `git repack -a` to copy all\n objects from the source repository into a pack in the cloned repository.\n \n---reference <repository>::\n-\tIf the reference repository is on the local machine,\n-\tautomatically setup `.git/objects/info/alternates` to\n-\tobtain objects from the reference repository.  Using\n-\tan already existing repository as an alternate will\n-\trequire fewer objects to be copied from the repository\n-\tbeing cloned, reducing network and local storage costs.\n-+\n-*NOTE*: see the NOTE for the `--shared` option.\n-\n---quiet::\n--q::\n-\tOperate quietly.  Progress is not reported to the standard\n-\terror stream. This flag is also passed to the `rsync'\n-\tcommand when given.\n-\n---verbose::\n--v::\n-\tRun verbosely. Does not affect the reporting of progress status\n-\tto the standard error stream.\n-\n---progress::\n-\tProgress status is reported on the standard error stream\n-\tby default when it is attached to a terminal, unless -q\n-\tis specified. This flag forces progress status even if the\n-\tstandard error stream is not directed to a terminal.\n-\n---no-checkout::\n--n::\n-\tNo checkout of HEAD is performed after the clone is complete.\n-\n---bare::\n-\tMake a 'bare' GIT repository.  That is, instead of\n-\tcreating `<directory>` and placing the administrative\n-\tfiles in `<directory>/.git`, make the `<directory>`\n-\titself the `$GIT_DIR`. This obviously implies the `-n`\n-\tbecause there is nowhere to check out the working tree.\n-\tAlso the branch heads at the remote are copied directly\n-\tto corresponding local branch heads, without mapping\n-\tthem to `refs/remotes/origin/`.  When this option is\n-\tused, neither remote-tracking branches nor the related\n-\tconfiguration variables are created.\n-\n---mirror::\n-\tSet up a mirror of the source repository.  This implies `--bare`.\n-\tCompared to `--bare`, `--mirror` not only maps local branches of the\n-\tsource to local branches of the target, it maps all refs (including\n-\tremote-tracking branches, notes etc.) and sets up a refspec configuration such\n-\tthat all these refs are overwritten by a `git remote update` in the\n-\ttarget repository.\n-\n---origin <name>::\n--o <name>::\n-\tInstead of using the remote name `origin` to keep track\n-\tof the upstream repository, use `<name>`.\n-\n---branch <name>::\n--b <name>::\n-\tInstead of pointing the newly created HEAD to the branch pointed\n-\tto by the cloned repository's HEAD, point to `<name>` branch\n-\tinstead. In a non-bare repository, this is the branch that will\n-\tbe checked out.\n+--template=<template_directory>::\n+\tSpecify the directory from which templates will be used;\n+\t(See the \"TEMPLATE DIRECTORY\" section of linkgit:git-init[1].)\n \n---upload-pack <upload-pack>::\n -u <upload-pack>::\n+--upload-pack <upload-pack>::\n \tWhen given, and the repository to clone from is accessed\n \tvia ssh, this specifies a non-default path for the command\n \trun on the other end.\n \n---template=<template_directory>::\n-\tSpecify the directory from which templates will be used;\n-\t(See the \"TEMPLATE DIRECTORY\" section of linkgit:git-init[1].)\n-\n---depth <depth>::\n-\tCreate a 'shallow' clone with a history truncated to the\n-\tspecified number of revisions.  A shallow repository has a\n-\tnumber of limitations (you cannot clone or fetch from\n-\tit, nor push from nor into it), but is adequate if you\n-\tare only interested in the recent history of a large project\n-\twith a long history, and would want to send in fixes\n-\tas patches.\n-\n---recursive::\n---recurse-submodules::\n-\tAfter the clone is created, initialize all submodules within,\n-\tusing their default settings. This is equivalent to running\n-\t`git submodule update --init --recursive` immediately after\n-\tthe clone is finished. This option is ignored if the cloned\n-\trepository does not have a worktree/checkout (i.e. if any of\n-\t`--no-checkout`/`-n`, `--bare`, or `--mirror` is given)\n+-v::\n+--verbose::\n+\tRun verbosely. Does not affect the reporting of progress status\n+\tto the standard error stream.\n \n <repository>::\n \tThe (possibly remote) repository to clone from.  See the\n-- \n1.7.2.3\n"}]}