Re: What is the idea for bare repositories?

From: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Date: Nov 12, 2007, 13:19 UTC
Message-ID: <20071112131927.GA1701@c3sl.ufpr.br>
In-Reply-To: <86k5on8v6p.fsf@lola.quinscape.zz>

A bare repository is the way to publish your changes to the public. git-daemon and http-clones use a bare repository that only contains adminsitrative files.

>From man page

       --bare Make a bare GIT repository. That is, instead of creating
              <directory> and placing the administrative files in
              <directory>/.git, make the <directory> itself the $GIT_DIR. This
              obviously implies the -n because there is nowhere to check out
              the working tree. Also the branch heads at the remote are copied
              directly to corresponding local branch heads, without mapping
              them to refs/remotes/origin/. When this option is used, neither
              remote-tracking branches nor the related configuration variables
              are created.

On Mon, Nov 12, 2007 at 02:11:58PM +0100, David Kastrup wrote:

Show 27 quoted lines

> 
> Hi,
> 
> I have a repository declared as bare.  Some commands treat it as such,
> other's don't.  For example, I get
> 
> git-diff [no complaint]
> git-status
> fatal: /usr/local/bin/git-status cannot be used without a working tree.
> git-reset [no complaint]
> git-reset --hard
> HEAD is now at db862c1... installmanager.sh: setze GIT_WORK_TREE
> git-commit
> fatal: /usr/local/bin/git-commit cannot be used without a working tree.
> git-add
> fatal: This operation must be run in a work tree
> 
> So this is all somewhat inconsistent.  What is the situation supposed
> to be?
> 
> -- 
> David Kastrup
> 
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Bruno Ribas - ribas@c3sl.ufpr.br
http://web.inf.ufpr.br/ribas
C3SL: http://www.c3sl.ufpr.br