git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txt

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 2, 2013, 16:08 UTC
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:
Show 14 quoted lines
> 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.

Show 9 quoted lines
>  
>  [[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"?

Previous: Thomas AckermannNext: Thomas Ackermann
Message 7 of 12 in “Some small fixes to glossary-content.txt”
  1. 0/3 Some small fixes to glossary-content.txtThomas Ackermann, Apr 2, 2013
  2. 1/3 Remove outdated/missleading/irrelevant entries from glossary-content.txtThomas Ackermann, Apr 2, 2013
  3. Junio C HamanoApr 2, 2013
  4. 2/3 Improve description of SHA1 related topics in glossary-content.txtThomas Ackermann, Apr 2, 2013
  5. Junio C HamanoApr 2, 2013
  6. 3/3 Remove definition of refspec and pathspec from glossary-content.txtThomas Ackermann, Apr 2, 2013
  7. Junio C HamanoApr 2, 2013
  8. Aw: Re: [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txtThomas Ackermann, Apr 2, 2013
  9. Junio C HamanoApr 2, 2013
  10. Aw: Re: Aw: Re: [PATCH 3/3] Remove definition of refspec and pathspec from glossary-content.txtThomas Ackermann, Apr 2, 2013
  11. Junio C HamanoApr 2, 2013
  12. Aw: Re: [PATCH 0/3] Some small fixes to glossary-content.txtThomas Ackermann, Apr 6, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.