Free Knowledge Resources


Linux Manual Pages


Free Software * Books

Source Code

Free Media

Linux

gitnamespaces(7)


NAME

   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 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'

SECURITY

   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).



Opportunity


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.



Free Software


Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.



Free Books


The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.



Education


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.


birds banner