{"thread":{"id":"25672","subject":"[PATCH/resend] Doc: git-push: Specify the default mode in the description","startedAt":"2010-11-08T13:20:35Z","lastAt":"2010-11-10T00:32:55Z","messageCount":5,"participants":["Santi Béjar","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"155378","messageId":"1289222435-9610-1-git-send-email-santi@agolina.net","threadId":"25672","inReplyTo":null,"subject":"[PATCH/resend] Doc: git-push: Specify the default mode in the description","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2010-11-08T13:20:35Z","receivedAt":"2010-11-08T13:20:35Z","isPatch":true,"sender":{"key":"santi@agolina.net","avatar":null},"body":"Signed-off-by: Santi Béjar <santi@agolina.net>\n---\nHi *,\n\n  just resend a patch that maybe was missed inside this thread:\n\nSubject:    possible bug when pushing with multiple remote repos.\nFrom:       Arnaud Mouiche\nDate:       2010-10-22 9:12:51\nhttp://marc.info/?i=1287738771.13348.34.camel%20()%20amolinux\n\nSanti\n\n Documentation/git-push.txt |    2 ++\n 1 files changed, 2 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex e11660a..9a2a93e 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -23,6 +23,8 @@ You can make interesting things happen to a repository\n every time you push into it, by setting up 'hooks' there.  See\n documentation for linkgit:git-receive-pack[1].\n \n+The default operation mode if no explicit refspec is found is\n+to push \"matching\" branches, see below.\n \n OPTIONS[[OPTIONS]]\n ------------------\n-- \n1.7.3.2.337.gc40334\n"},{"id":"155431","messageId":"7vy693o833.fsf@alter.siamese.dyndns.org","threadId":"25672","inReplyTo":"1289222435-9610-1-git-send-email-santi@agolina.net","subject":"Re: [PATCH/resend] Doc: git-push: Specify the default mode in the description","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-11-08T20:48:16Z","receivedAt":"2010-11-08T20:48:16Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Santi Béjar <santi@agolina.net> writes:\n\n> Signed-off-by: Santi Béjar <santi@agolina.net>\n> ---\n> Hi *,\n>\n>   just resend a patch that maybe was missed inside this thread:\n\nNo, I didn't miss it.\n\nThe new text says 'push \"matching\" branches' before explaining what it is,\nonly vaguely refers the reader to the next section by \"see below\" without\ntelling which part of below the reader should look at.  In other words, it\nwastes two lines without adding two lines worth of additional information.\n\nSaying \"look for string 'default' below\" might be an improvement ;-), but\nthen the reader can do that without being told to do so themselves, so...\n\n> Subject:    possible bug when pushing with multiple remote repos.\n> From:       Arnaud Mouiche\n> Date:       2010-10-22 9:12:51\n> http://marc.info/?i=1287738771.13348.34.camel%20()%20amolinux\n>\n> Santi\n>\n>  Documentation/git-push.txt |    2 ++\n>  1 files changed, 2 insertions(+), 0 deletions(-)\n>\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index e11660a..9a2a93e 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -23,6 +23,8 @@ You can make interesting things happen to a repository\n>  every time you push into it, by setting up 'hooks' there.  See\n>  documentation for linkgit:git-receive-pack[1].\n>  \n> +The default operation mode if no explicit refspec is found is\n> +to push \"matching\" branches, see below.\n>  \n>  OPTIONS[[OPTIONS]]\n>  ------------------\n> -- \n> 1.7.3.2.337.gc40334\n"},{"id":"155480","messageId":"AANLkTimYTRvOb1SjjUyANuTX2sCRKj17bLMbkKKG3rFg@mail.gmail.com","threadId":"25672","inReplyTo":"7vy693o833.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH/resend] Doc: git-push: Specify the default mode in the description","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2010-11-09T12:23:20Z","receivedAt":"2010-11-09T12:23:20Z","isPatch":true,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On Mon, Nov 8, 2010 at 9:48 PM, Junio C Hamano <gitster@pobox.com> wrote:\n> Santi Béjar <santi@agolina.net> writes:\n>\n>> Signed-off-by: Santi Béjar <santi@agolina.net>\n>> ---\n>> Hi *,\n>>\n>>   just resend a patch that maybe was missed inside this thread:\n>\n> No, I didn't miss it.\n>\n> The new text says 'push \"matching\" branches' before explaining what it is,\n> only vaguely refers the reader to the next section by \"see below\" without\n> telling which part of below the reader should look at.  In other words, it\n> wastes two lines without adding two lines worth of additional information.\n>\n> Saying \"look for string 'default' below\" might be an improvement ;-), but\n> then the reader can do that without being told to do so themselves, so...\n\nAt least with the new text the reader will know what to look for. She\nhas to look for \"matching\" and not the generic \"default\". BTW, I'll\nsend another patch with the explanation of matching, but it just\nrepeats what is written in the <refspec> option...\n\nAnother option would be to add \"see the <refspec> option below\",\nalthough is is already implicit as the paragraph begins with \"if no\nexplicit refspec\".\n\nSanti\n"},{"id":"155481","messageId":"1289305497-13883-1-git-send-email-santi@agolina.net","threadId":"25672","inReplyTo":"AANLkTimYTRvOb1SjjUyANuTX2sCRKj17bLMbkKKG3rFg@mail.gmail.com","subject":"[PATCHv2] Doc: git-push: Specify the default mode in the description","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2010-11-09T12:24:57Z","receivedAt":"2010-11-09T12:24:57Z","isPatch":false,"sender":{"key":"santi@agolina.net","avatar":null},"body":"Text extracted from the <refspec> option.\n\nSigned-off-by: Santi Béjar <santi@agolina.net>\n---\n Documentation/git-push.txt |    5 +++++\n 1 files changed, 5 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex e11660a..2c0b311 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -23,6 +23,11 @@ You can make interesting things happen to a repository\n every time you push into it, by setting up 'hooks' there.  See\n documentation for linkgit:git-receive-pack[1].\n \n+The default operation mode if no explicit refspec is found is\n+to push \"matching\" branches, that is for every branch that exists on\n+the local side, the remote side is updated if a branch of the same name\n+already exists on the remote side. See the <refspec> option below for\n+more details.\n \n OPTIONS[[OPTIONS]]\n ------------------\n-- \n1.7.3.2.337.gc40334\n"},{"id":"155555","messageId":"7vd3qej9vs.fsf@alter.siamese.dyndns.org","threadId":"25672","inReplyTo":"1289305497-13883-1-git-send-email-santi@agolina.net","subject":"Re: [PATCHv2] Doc: git-push: Specify the default mode in the description","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-11-10T00:32:55Z","receivedAt":"2010-11-10T00:32:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Santi Béjar <santi@agolina.net> writes:\n\n> Text extracted from the <refspec> option.\n\nPerhaps I wasn't clear enough.  \"extracted\" is not something we want.\n\nIf you think \"'matching' is the default\" is so important than anything\nelse, explaining it upfront _might_ be a good idea, but then why leave the\noriginal description only to repeat the same thing again?\n\nIt would be an improvement if you rephrased things so that the manual\nbecomes shorter, non repetitive, and having more important information\neasier to find.  Otherwise it's just adding noise on top of noise that\nalready is there, isn't it?\n"}]}