git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Unify the name of the second option in the text
Date: Sun, 03 Feb 2008 04:04:34 -0800 (PST)	[thread overview]
Message-ID: <m3y7a25jqt.fsf@localhost.localdomain> (raw)
In-Reply-To: <1201996688-5559-3-git-send-email-joerg@alea.gnuu.de>

Jörg Sommer <joerg@alea.gnuu.de> writes:

> Signed-off-by: Jörg Sommer <joerg@alea.gnuu.de>
> ---
>  Documentation/git-push.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index 5f24944..18e0c06 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -53,7 +53,7 @@ side are updated.
>  +
>  `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
>  +
> -A parameter <ref> without a colon pushes the <ref> from the source
> +A parameter <refspec> without a colon pushes the <refspec> from the source
>  repository to the destination repository under the same name.
>  +
>  Pushing an empty <src> allows you to delete the <dst> ref from

Err... that is incorrect without further surgery. <refspec> is either
<ref>:<ref>, <ref> or some other exotic case; in the form <ref>:<ref>
it can include globbing. The fragment above talks about situation
where <refspec> is <ref>, and does not contain colon.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      reply	other threads:[~2008-02-03 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 23:58 [PATCH] Fix spelling mistake; flagg -> flag Jörg Sommer
2008-02-02 23:58 ` [PATCH] Unify the argument of the parameter -m Jörg Sommer
2008-02-02 23:58   ` [PATCH] Unify the name of the second option in the text Jörg Sommer
2008-02-03 12:04     ` Jakub Narebski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3y7a25jqt.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=joerg@alea.gnuu.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).