From: Zack Brown <zbrown@tumblerings.org>
Date: Sun, 05 Jun 2005 18:29:12 GMT
Subject: Re: cg-init bug -- identified
Message-ID: <20050605182912.GC6890@tumblerings.org>
In-Reply-To: <20050605181042.GH17462@pasky.ji.cz>

On Sun, Jun 05, 2005 at 08:10:42PM +0200, Petr Baudis wrote:
> Dear diary, on Sun, Jun 05, 2005 at 07:56:34PM CEST, I got a letter
> where Zack Brown <zbrown@tumblerings.org> told me that...
> > Depending on how I check, I get very different lists. I'll include both in this email.
> > 
> > If I do the 'cg-init' on the full source.cogito directory, then do a 'cg-clone'
> > into a new source.cogtst directory, here is the result of a comparison:
> 
> Hmm. That's very strange, I can't see what could be the problem. If you
> try cg-init multiple times, do you always get the same list of files
> missed out? Can you spot any error messages while doing cg-init?

I figured it out.

I made a temporary copy of the directory, and kept doing

$ rm -rf .git
$ rm somerandomfileordir
$ cg-init
$ cg-status

It turned out one of my files had a "'" in the name, i.e.:

$ ls
Zack's_file
$

I removed it, and all of a sudden cg-init worked perfectly.

Is that a Cogito bug? I would expect git to handle any filename the filesystem
itself can handle.

Be well,
Zack

> 
> -- 
> 				Petr "Pasky" Baudis
> Stuff: http://pasky.or.cz/
> C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
> -
> 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

-- 
Zack Brown