{"thread":{"id":"17237","subject":"[PATCH 0/4] Clarifying the refspec documentation","startedAt":"2009-01-18T14:36:54Z","lastAt":"2009-01-19T03:46:02Z","messageCount":6,"participants":["Anders Melchiorsen","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":4},"messages":[{"id":"100969","messageId":"1232289418-25627-1-git-send-email-mail@cup.kalibalik.dk","threadId":"17237","inReplyTo":null,"subject":"[PATCH 0/4] Clarifying the refspec documentation","fromName":"Anders Melchiorsen","fromEmail":"mail@cup.kalibalik.dk","sentAt":"2009-01-18T14:36:54Z","receivedAt":"2009-01-18T14:36:54Z","isPatch":true,"sender":{"key":"mail@cup.kalibalik.dk","avatar":null},"body":"This is a partial resend of some small updates to the git-push\nrefspec documentation. I have removed the parts of the patch\nseries that had comments last time, and will rework those later.\n\nMeanwhile, I think that these simple modification do help in\nmaking things more readable. Once you understand the refspec, it\nis hard to realize how hard those few paragraphs are to digest.\n\n\nAnders Melchiorsen (4):\n Documentation: git push repository can also be a remote\n Documentation: remove a redundant elaboration\n Documentation: mention branches rather than heads\n Documentation: avoid using undefined parameters\n\n Documentation/git-push.txt | 15 ++++++++-------\n 1 files changed, 8 insertions(+), 7 deletions(-)\n"},{"id":"100970","messageId":"1232289418-25627-2-git-send-email-mail@cup.kalibalik.dk","threadId":"17237","inReplyTo":"1232289418-25627-1-git-send-email-mail@cup.kalibalik.dk","subject":"[PATCH 1/4] Documentation: git push repository can also be a remote","fromName":"Anders Melchiorsen","fromEmail":"mail@cup.kalibalik.dk","sentAt":"2009-01-18T14:36:55Z","receivedAt":"2009-01-18T14:36:55Z","isPatch":true,"sender":{"key":"mail@cup.kalibalik.dk","avatar":null},"body":"This is copied from pull-fetch-param.txt and helps the reader\nto not get stuck in the URL section.\n\nSigned-off-by: Anders Melchiorsen \n---\n Documentation/git-push.txt | 4 +++-\n 1 files changed, 3 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 3321966..8bfa7cb 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -28,7 +28,9 @@ OPTIONS\n -------\n ::\n \tThe \"remote\" repository that is destination of a push\n-\toperation. See the section <> below.\n+\toperation. This parameter can be either a URL\n+\t(see the section <> below) or the name\n+\tof a remote (see the section <> below).\n \n ...::\n \tThe canonical format of a parameter is\n-- \n1.6.0.2.514.g23abd3\n"},{"id":"100972","messageId":"1232289418-25627-3-git-send-email-mail@cup.kalibalik.dk","threadId":"17237","inReplyTo":"1232289418-25627-2-git-send-email-mail@cup.kalibalik.dk","subject":"[PATCH 2/4] Documentation: remove a redundant elaboration","fromName":"Anders Melchiorsen","fromEmail":"mail@cup.kalibalik.dk","sentAt":"2009-01-18T14:36:56Z","receivedAt":"2009-01-18T14:36:56Z","isPatch":true,"sender":{"key":"mail@cup.kalibalik.dk","avatar":null},"body":"The comment in parentheses is wrong, as one has to leave out both the\ncolon and . This situation is covered by the section a few lines\ndown:\n\n A parameter without a colon pushes the from the source\n repository to the destination repository under the same name.\n\nSo, just remove the parentheses.\n\nSigned-off-by: Anders Melchiorsen \n---\n Documentation/git-push.txt | 3 +--\n 1 files changed, 1 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 8bfa7cb..6d3c711 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -44,8 +44,7 @@ tip of `master` branch); see linkgit:git-rev-parse[1]) that you\n want to push. The side represents the destination location.\n +\n The local ref that matches is used\n-to fast forward the remote ref that matches (or, if no was\n-specified, the same ref that referred to locally). If\n+to fast forward the remote ref that matches . If\n the optional leading plus `+` is used, the remote ref is updated\n even if it does not result in a fast forward update.\n +\n-- \n1.6.0.2.514.g23abd3\n"},{"id":"100973","messageId":"1232289418-25627-4-git-send-email-mail@cup.kalibalik.dk","threadId":"17237","inReplyTo":"1232289418-25627-3-git-send-email-mail@cup.kalibalik.dk","subject":"[PATCH 3/4] Documentation: mention branches rather than heads","fromName":"Anders Melchiorsen","fromEmail":"mail@cup.kalibalik.dk","sentAt":"2009-01-18T14:36:57Z","receivedAt":"2009-01-18T14:36:57Z","isPatch":true,"sender":{"key":"mail@cup.kalibalik.dk","avatar":null},"body":"Most of the git push page talks about branches, so make it consistent\nalso in this paragraph.\n\nSigned-off-by: Anders Melchiorsen \n---\n Documentation/git-push.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 6d3c711..a7a6f4c 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -57,8 +57,8 @@ Pushing an empty allows you to delete the ref from\n the remote repository.\n +\n The special refspec `:` (or `+:` to allow non-fast forward updates)\n-directs git to push \"matching\" heads: for every head that exists on\n-the local side, the remote side is updated if a head of the same name\n+directs git to push \"matching\" branches: 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. This is the default operation mode\n if no explicit refspec is found (that is neither on the command line\n nor in any Push line of the corresponding remotes file---see below).\n-- \n1.6.0.2.514.g23abd3\n"},{"id":"100971","messageId":"1232289418-25627-5-git-send-email-mail@cup.kalibalik.dk","threadId":"17237","inReplyTo":"1232289418-25627-4-git-send-email-mail@cup.kalibalik.dk","subject":"[PATCH 4/4] Documentation: avoid using undefined parameters","fromName":"Anders Melchiorsen","fromEmail":"mail@cup.kalibalik.dk","sentAt":"2009-01-18T14:36:58Z","receivedAt":"2009-01-18T14:36:58Z","isPatch":true,"sender":{"key":"mail@cup.kalibalik.dk","avatar":null},"body":"The parameter has not been introduced, so rewrite to\navoid it.\n\nSigned-off-by: Anders Melchiorsen \n---\n Documentation/git-push.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex a7a6f4c..7b27dc6 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -50,8 +50,8 @@ even if it does not result in a fast forward update.\n +\n `tag ` means the same as `refs/tags/:refs/tags/`.\n +\n-A parameter without a colon pushes the from the source\n-repository to the destination repository under the same name.\n+A lonely parameter (without a colon and a destination) pushes\n+the to the same name in the destination repository.\n +\n Pushing an empty allows you to delete the ref from\n the remote repository.\n-- \n1.6.0.2.514.g23abd3\n"},{"id":"101091","messageId":"7vhc3wrm9x.fsf@gitster.siamese.dyndns.org","threadId":"17237","inReplyTo":"1232289418-25627-4-git-send-email-mail@cup.kalibalik.dk","subject":"Re: [PATCH 3/4] Documentation: mention branches rather than heads","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-01-19T03:46:02Z","receivedAt":"2009-01-19T03:46:02Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Anders Melchiorsen writes:\n\n> Most of the git push page talks about branches, so make it consistent\n> also in this paragraph.\n\n> Signed-off-by: Anders Melchiorsen \n> ---\n> Documentation/git-push.txt | 4 ++--\n> 1 files changed, 2 insertions(+), 2 deletions(-)\n>\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index 6d3c711..a7a6f4c 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -57,8 +57,8 @@ Pushing an empty allows you to delete the ref from\n> the remote repository.\n> +\n> The special refspec `:` (or `+:` to allow non-fast forward updates)\n> -directs git to push \"matching\" heads: for every head that exists on\n> -the local side, the remote side is updated if a head of the same name\n> +directs git to push \"matching\" branches: 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. This is the default operation mode\n> if no explicit refspec is found (that is neither on the command line\n> nor in any Push line of the corresponding remotes file---see below).\n\nConsistency is good, and I agree \"head\" may be suboptimal here as this\npart tries to give formal semantics to what various refspecs do.\n\nI first thought it would make more sense to say \"ref\" instead, just like\nthe previous paragraph that talks about : form explains it is a way\nto remove a \"ref\". But we do only matching branches with : syntax these\ndays since 098e711 (\"git-push $URL\" without refspecs pushes only matching\nbranches, 2007-07-01); I agree with the updated text for that reason, but\nI think the commit log message is wrong.\n\nThanks.\n"}]}