From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 02 Apr 2013 16:08:12 GMT
Subject: Re: [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txt
Message-ID: <7vy5d0gbkj.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1622068154.727718.1364894924364.JavaMail.ngmail@webmail14.arcor-online.net>

Thomas Ackermann <th.acker@arcor.de> writes:

> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
> ---
>  Documentation/glossary-content.txt | 65 ++------------------------------------
>  1 file changed, 3 insertions(+), 62 deletions(-)
>
> diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
> index 05bfebc..1c9c522 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -261,59 +261,7 @@ This commit is referred to as a "merge commit", or sometimes just a
>  	pack.
>  
>  [[def_pathspec]]pathspec::
> +       Pattern used to specify paths in Git commands.

Strictly speaking, it is "used to limit", but in the context of this
document it shouldn't matter either way.

>  
>  [[def_parent]]parent::
>  	A <<def_commit_object,commit object>> contains a (possibly empty) list
> @@ -382,15 +330,8 @@ should not be combined with other pathspec.
>  [[def_refspec]]refspec::
>  	A "refspec" is used by <<def_fetch,fetch>> and
>  	<<def_push,push>> to describe the mapping between remote
> +	<<def_ref,ref>> and local ref. 
> +	See linkgit:git-push[1] for details.

I think we can just drop "See ... for details" from here.  Besides,
why just "push" and not "fetch"?