Section 7: overview, conventions, and miscellany
glob – globbing pathnames Description Long ago, in UNIX V6, there was a program /etc/glob that would expand wildcard patterns. Soon afterward this became a shell built-in. These days there is also a library routine glob(3) that will perform this function for a user program. The rules are as follows (POSIX.2, 3.13). Wildcard matching A…
libc – overview of standard C libraries on Linux Description The term "libc" is commonly used as a shorthand for the "standard C library", a library of standard functions that can be used by all C programs (and sometimes by programs in other languages). Because of some history (see below), use of the term "libc"…
gitworkflows – An overview of recommended workflows with Git Synopsis git * Description This document attempts to write down and motivate some of the workflow elements used for git.git itself. Many ideas apply in general, though the full workflow is rarely required for smaller projects with fewer people involved. We formulate a set of rules…
gittutorial – A tutorial introduction to Git Synopsis git * Description This tutorial explains how to import a new project into Git, make changes to it, and share changes with other developers. If you are instead primarily interested in using Git to fetch a project, for example, to test the latest version, you may prefer…
gittutorial-2 – A tutorial introduction to Git: part two Synopsis git * Description You should work through gittutorial(7) before reading this tutorial. The goal of this tutorial is to introduce two fundamental pieces of Git’s architecture—the object database and the index file—and to provide the reader with everything necessary to understand the rest of the…
gitsubmodules – Mounting one repository inside another Synopsis .gitmodules, $GIT_DIR/config git submodule git <command> –recurse-submodules Description A submodule is a repository embedded inside another repository. The submodule has its own history; the repository it is embedded in is called a superproject. On the filesystem, a submodule usually (but not always – see FORMS below) consists…
gitrevisions – Specifying revisions and ranges for Git Synopsis gitrevisions Description Many Git commands take revision parameters as arguments. Depending on the command, they denote a specific commit or, for commands which walk the revision graph (such as git-log(1)), all commits which are reachable from that commit. For commands that walk the revision graph one…
gitremote-helpers – Helper programs to interact with remote repositories Synopsis git remote-<transport> <repository> [<URL>] Description Remote helper programs are normally not used directly by end users, but they are invoked by Git when it needs to interact with remote repositories Git does not support natively. A given helper will implement a subset of the capabilities…
gitnamespaces – Git namespaces Synopsis GIT_NAMESPACE=<namespace> git upload-pack GIT_NAMESPACE=<namespace> git receive-pack Description Git supports dividing the refs of a single repository into multiple namespaces, each of which has its own branches, tags, and HEAD. Git can expose each namespace as an independent repository to pull from and push to, while sharing the object store, and…
gitglossary – A Git Glossary Synopsis * Description alternate object database Via the alternates mechanism, a repository can inherit part of its object database from another object database, which is called an "alternate". bare repository A bare repository is normally an appropriately named directory with a .git suffix that does not have a locally checked-out…
gitfaq – Frequently asked questions about using Git Synopsis gitfaq Description The examples in this FAQ assume a standard POSIX shell, like bash or dash, and a user, A U Thor, who has the account author on the hosting provider git.example.org. Configuration What should I put in user.name? You should put your personal name, generally…
giteveryday – A useful minimum set of commands for Everyday Git Synopsis Everyday Git With 20 Commands Or So Description Git users can broadly be grouped into four categories for the purposes of describing here a small set of useful command for everyday Git. • Individual Developer (Standalone) commands are essential for anybody who makes…
gitdiffcore – Tweaking diff output Synopsis git diff * Description The diff commands git diff-index, git diff-files, and git diff-tree can be told to manipulate differences they find in unconventional ways before showing diff output. The manipulation is collectively called "diffcore transformation". This short note describes what they are and how to use them to…
gitcvs-migration – Git for CVS users Synopsis git cvsimport * Description Git differs from CVS in that every working tree contains a repository with a full copy of the project history, and no repository is inherently more important than any other. However, you can emulate the CVS model by designating a single shared repository which…
gitcredentials – Providing usernames and passwords to Git Synopsis git config credential.https://example.com.username myusername git config credential.helper "$helper $options" Description Git will sometimes need credentials from the user in order to perform operations; for example, it may need to ask for a username and password in order to access a remote repository over HTTP. This manual…
gitcore-tutorial – A Git core tutorial for developers Synopsis git * Description This tutorial explains how to use the "core" Git commands to set up and work with a Git repository. If you just need to use Git as a revision control system you may prefer to start with "A Tutorial Introduction to Git" (gittutorial(7))…
gitcli – Git command-line interface and conventions Synopsis gitcli Description This manual describes the convention used throughout Git CLI. Many commands take revisions (most often "commits", but sometimes "tree-ish", depending on the context and command) and paths as their arguments. Here are the rules: • Revisions come first and then paths. E.g. in git diff…
ggz – The GGZ Gaming Zone Description The GGZ Gaming Zone is a standards-conforming free online gaming infrastructure which provides many applications and games to people who like to play on the internet or in local networks. GGZ, how the (recursive) acronym is called, is available for many computer systems. This document focuses on the…
gammu-smsd-tables – description of tables for database backends of gammu-smsd(1) Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). Separate backends are described in their appropriate man pages. This manual page describes general database structure and required tables. More SMS daemons can share single database. If you do not specify…
gammu-smsd-pgsql – gammu-smsd(1) backend using PostgreSQL database server as a message storage Description gammu-smsd(1) supports several backends. Actual backend is chosen in a config file gammu-smsdrc(5). PGSQL backend stores all data in a PostgreSQL database server, which parameters are defined by configuration (see gammu-smsdrc(5) for description of configuration options). For tables description see gammu-smsd-tables(7). See…