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

RE: git & patterns

From
TMTim Mazid <timmazid@hotmail.com>
Date
May 19, 2011, 06:40 UTC
Message-ID
<SNT124-w95A0758AAE98C128DB9A2C48E0@phx.gbl>
In-Reply-To
<4DD4B772.2050404@hupie.com>

Sorry; just thought I'd chime in as a "regular" git user; one who actually has to read the documentation to figure things out instead just knowing it because they helped code it.

Show 13 quoted lines
> >> - could the manual page be update to make this explicit please? (plus
> >> other manual pages talking about (shell) patterns)
> >
> > The general design guideline we have is to use glob for things that look
> > like pathnames. Refs, refspecs, ignore and attribute rules are the
> > examples of this rule.
> >
>
> Well, to me tags do not look like pathnames at all, they're just
> 'random' strings. As are branches.
> Technically they may be like pathnames because they're projected on to
> the filesystem that way, but principally they're not IMHO: it's an
> implementation detail.

I must agree here. As a non-git-developer, I did not think of tags or branches as pathnames.

Show 14 quoted lines
> > We may be lacking this info in our documentation. A patch to add it
> > somewhere is very welcome.
>
> Yesterday I already did a quick grep on pattern and glob in the
> documentation directory and found that:
> - usually patterns are just patterns, without specifying what kind
> - when a pattern type is specified it most of the time is a glob pattern
> - but sometimes it is called a shell pattern
> - and a few cases speak of a wildcard pattern (I think)
>
> What should it be?
> From your comments I gather it should be a glob pattern.
> Isn't glob too 'tech speak' or is it acceptable?
> If not acceptable, then what? Shell wildcard pattern?

I would not say that glod is too tech speak, as long is it was clearly explained somewhere easily accessible. If it's never explained, or buried deep within the manpage for some random command, then it certainly should not be assumed that the reader knows what it is.

Speaking of which, I'm still not too sure what a glob is.

Is there a "concepts" or "glossary" man page or similar somewhere that explains all the terms used in git that an "outsider" (somebody who does not develop git and just began to use it) might not be aware of?

If there is not, might I suggest it be a good idea to include one as well references to it so that a rookie will know they should look there for explanations of terms?

Tim.
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
 		 	   		  
Previous: Ferry HubertsNext: Tim Mazid
Message 6 of 11 in “git & patterns”
  1. Ferry HubertsMay 18, 2011
  2. Andreas EricssonMay 18, 2011
  3. Ferry HubertsMay 18, 2011
  4. Junio C HamanoMay 18, 2011
  5. Ferry HubertsMay 19, 2011
  6. Tim MazidMay 19, 2011
  7. Tim MazidMay 19, 2011
  8. Ferry HubertsMay 19, 2011
  9. Tim MazidMay 19, 2011
  10. Junio C HamanoMay 19, 2011
  11. Ferry HubertsMay 19, 2011

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.