{"thread":{"id":"23361","subject":"[PATCH] Docs: Describe omitted <repository> behavior in a prominent place","startedAt":"2010-04-06T19:32:29Z","lastAt":"2010-04-08T18:07:53Z","messageCount":2,"participants":["Ori Avtalion"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"138776","messageId":"4bbb8fa3.0f1abc0a.2383.7991@mx.google.com","threadId":"23361","inReplyTo":null,"subject":"[PATCH] Docs: Describe omitted <repository> behavior in a prominent place","fromName":"Ori Avtalion","fromEmail":"ori@avtalion.name","sentAt":"2010-04-06T19:32:29Z","receivedAt":"2010-04-06T19:32:29Z","isPatch":true,"sender":{"key":"ori@avtalion.name","avatar":"https://avatars.githubusercontent.com/u/28355?v=4"},"body":"The documentation of which repository is pushed to when the repository\nflag is omitted was only mentioned under the --repo flag.\n\nIt is now described under the <repository> argument.\n\nSigned-off-by: Ori Avtalion <ori@avtalion.name>\n---\n Documentation/git-push.txt |   15 +++++++++------\n 1 files changed, 9 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 59dc8b1..14d286e 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -31,6 +31,11 @@ OPTIONS[[OPTIONS]]\n \toperation.  This parameter can be either a URL\n \t(see the section <<URLS,GIT URLS>> below) or the name\n \tof a remote (see the section <<REMOTES,REMOTES>> below).\n++\n+If omitted, 'git push' derives the remote name from the current\n+branch: If it tracks a remote branch, then that remote repository\n+is pushed to. Otherwise, the name \"origin\" is used. This can be\n+overridden with the `--repo` option.\n \n <refspec>...::\n \tThe format of a <refspec> parameter is an optional plus\n@@ -116,12 +121,10 @@ nor in any Push line of the corresponding remotes file---see below).\n \n --repo=<repository>::\n \tThis option is only relevant if no <repository> argument is\n-\tpassed in the invocation. In this case, 'git push' derives the\n-\tremote name from the current branch: If it tracks a remote\n-\tbranch, then that remote repository is pushed to. Otherwise,\n-\tthe name \"origin\" is used. For this latter case, this option\n-\tcan be used to override the name \"origin\". In other words,\n-\tthe difference between these two commands\n+\tpassed in the invocation, and the current branch does not track\n+\ta remote branch. For this case, this option can be used to \n+\toverride the name \"origin\". In other words, the difference\n+\tbetween these two commands\n +\n --------------------------\n git push public         #1\n-- \n1.7.0\n"},{"id":"138975","messageId":"4BBE1B79.2090902@avtalion.name","threadId":"23361","inReplyTo":"4bbb8fa3.0f1abc0a.2383.7991@mx.google.com","subject":"Re: [PATCH] Docs: Describe omitted <repository> behavior in a prominent place","fromName":"Ori Avtalion","fromEmail":"ori@avtalion.name","sentAt":"2010-04-08T18:07:53Z","receivedAt":"2010-04-08T18:07:53Z","isPatch":true,"sender":{"key":"ori@avtalion.name","avatar":"https://avatars.githubusercontent.com/u/28355?v=4"},"body":"On 04/06/2010 10:32 PM, Ori Avtalion wrote:\n> The documentation of which repository is pushed to when the repository\n> flag is omitted was only mentioned under the --repo flag.\n>\n> It is now described under the <repository>  argument.\n\nDoes anyone want to comment on this patch? It seems to get lost in the \nflood.\n"}]}