gitnamespaces - Git namespaces


   GIT_NAMESPACE=<namespace> git upload-pack
   GIT_NAMESPACE=<namespace> git receive-pack


   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 exposing all the refs to
   operations such as git-gc(1).

   Storing multiple repositories as namespaces of a single repository
   avoids storing duplicate copies of the same objects, such as when
   storing multiple branches of the same source. The alternates mechanism
   provides similar support for avoiding duplicates, but alternates do not
   prevent duplication between new objects added to the repositories
   without ongoing maintenance, while namespaces do.

   To specify a namespace, set the GIT_NAMESPACE environment variable to
   the namespace. For each ref namespace, Git stores the corresponding
   refs in a directory under refs/namespaces/. For example,
   GIT_NAMESPACE=foo will store refs under refs/namespaces/foo/. You can
   also specify namespaces via the --namespace option to git(1).

   Note that namespaces which include a / will expand to a hierarchy of
   namespaces; for example, GIT_NAMESPACE=foo/bar will store refs under
   refs/namespaces/foo/refs/namespaces/bar/. This makes paths in
   GIT_NAMESPACE behave hierarchically, so that cloning with
   GIT_NAMESPACE=foo/bar produces the same result as cloning with
   GIT_NAMESPACE=foo and cloning from that repo with GIT_NAMESPACE=bar. It
   also avoids ambiguity with strange namespace paths such as
   foo/refs/heads/, which could otherwise generate directory/file
   conflicts within the refs directory.

   git-upload-pack(1) and git-receive-pack(1) rewrite the names of refs as
   specified by GIT_NAMESPACE. git-upload-pack and git-receive-pack will
   ignore all references outside the specified namespace.

   The smart HTTP server, git-http-backend(1), will pass GIT_NAMESPACE
   through to the backend programs; see git-http-backend(1) for sample
   configuration to expose repository namespaces as repositories.

   For a simple local test, you can use git-remote-ext(1):

       git clone ext::'git --namespace=foo %s /tmp/prefixed.git'


   Anyone with access to any namespace within a repository can potentially
   access objects from any other namespace stored in the same repository.
   You can't directly say "give me object ABCD" if you don't have a ref to
   it, but you can do some other sneaky things like:

    1. Claiming to push ABCD, at which point the server will optimize out
       the need for you to actually send it. Now you have a ref to ABCD
       and can fetch it (claiming not to have it, of course).

    2. Requesting other refs, claiming that you have ABCD, at which point
       the server may generate deltas against ABCD.

   None of this causes a problem if you only host public repositories, or
   if everyone who may read one namespace may also read everything in
   every other namespace (for instance, if everyone in an organization has
   read permission to every repository).

More Linux Commands

gtf(1) - calculate VESA GTF mode lines - Linux manual page
Gtf is a utility for calculating VESA GTF modes. Given the desired horizontal and vertical resolutions and refresh rate (in Hz), the parameters for a matching V

gnutls_pkcs11_privkey_get_info(3) - API function (Man Page)
This function will return information about the PKCS 11 private key such as the label, id as well as token information where the key is stored. When output is t

telnet(1) - user interface to the TELNET protocol (ManPage)
The telnet command is used to communicate with another host using the TELNET protocol. If telnet is invoked without the host argument, it enters command mode, i

git-update-ref(1) - Update the object name stored in a ref s
Given two arguments, stores the &lt;newvalue&gt; in the &lt;ref&gt;, possibly dereferencing the symbolic refs. E.g. git update-ref HEAD &lt;newvalue&gt; updates the current branc

syncok(3ncurses) - create curses windows - Linux man page...
Calling newwin creates and returns a pointer to a new window with the given number of lines and columns. The upper left-hand corner of the window is at line beg

snmp_select_info(3) - netsnmp_session_api functions.........
Snmp_sess_init prepares a netsnmp_session that sources transport characteristics and common information that will be used for a set of SNMP transactions. After

sane-fujitsu(5) - SANE backend for Fujitsu flatbed and ADF s
The sane-fujitsu library implements a SANE (Scanner Access Now Easy) backend which provides access to most Fujitsu flatbed and ADF scanners. This document descr

editres(1) - a dynamic resource editor for X Toolkit applica
Editres is a tool that allows users and application developers to view the full widget hierarchy of any X Toolkit application that speaks the Editres protocol.

asn1_find_node(3) - API function (Library - Linux man page)
Searches for an element called name starting from pointer . The name is composed by differents identifiers separated by dots. When * pointer has a name, the fir

menubutton(n) - Create and manipulate menubutton widgets....
The menubutton command creates a new window (given by the pathName argument) and makes it into a menubutton widget. Additional options, described above, may be

ispunct(3) - character classification routines (Man Page)...
These functions check whether c, which must have the value of an unsigned char or EOF, falls into a certain character class according to the specified locale. T

Tcl_DictObjGet(3) - manipulate Tcl objects as dictionaries
Tcl dictionary objects have an internal representation that supports efficient mapping from keys to values and which guarantees that the particular ordering of

We can't live, work or learn in freedom unless the software we use is free.