On Monday 12 November 2007 14:57, Johannes Schindelin wrote: > Hi, > > On Mon, 12 Nov 2007, Bruno Cesar Ribas wrote: > > 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. > > More to the point, a bare repository is one which does not have a working > directory attached. > > As such, many commands do not make any sense at all, such as "git add" > (_what_ do you want to add? There is not even a working directory to work > with!), or "git commit". As we are on the subject anyway. Though not tested with the very latest, but when I was playing with them, I found out that cloning a empty bare repository produces nothing at all, dispite the promising message: $ mkdir x && cd x $ git --bare init --shared=group Initialized empty shared Git repository in /home/nobackup/jan/tmp/x/ $ cd .. $ git clone x y Initialized empty Git repository in /home/jan/nobackup/tmp/y/.git/ $ ls y ls: cannot access y: No such file or directory Is this a bug? --- Jan - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
