From: Petr Baudis <pasky@ucw.cz>
To: Zack Brown <zbrown@tumblerings.org>
Cc: git@vger.kernel.org
Subject: Re: cg-init bug -- identified
Date: Sun, 5 Jun 2005 22:19:04 +0200 [thread overview]
Message-ID: <20050605201904.GL17462@pasky.ji.cz> (raw)
In-Reply-To: <20050605182912.GC6890@tumblerings.org>
Dear diary, on Sun, Jun 05, 2005 at 08:29:12PM CEST, I got a letter
where Zack Brown <zbrown@tumblerings.org> told me that...
> 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.
Could you check with the latest Cogito, please?
(88467971134efddf66793ba44c4ee1ffc7573a0a)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-06-05 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 15:30 cg-init bug Zack Brown
2005-06-05 16:10 ` Radoslaw Szkodzinski
2005-06-05 16:27 ` Zack Brown
2005-06-05 17:59 ` Radoslaw Szkodzinski
2005-06-05 17:28 ` Petr Baudis
2005-06-05 17:56 ` Zack Brown
2005-06-05 18:10 ` Petr Baudis
2005-06-05 18:29 ` cg-init bug -- identified Zack Brown
2005-06-05 18:43 ` Tommy M. McGuire
2005-06-05 19:09 ` Tommy M. McGuire
2005-06-05 19:22 ` [PATCH] " Tommy M. McGuire
2005-06-05 19:15 ` [PATCH] Make cg-add use xargs -0 Dan Holmsand
2005-06-05 20:19 ` Petr Baudis [this message]
2005-06-05 23:52 ` cg-init bug -- identified and fixed - thanks! Zack Brown
2005-06-05 21:11 ` cg-init bug -- identified Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050605201904.GL17462@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=zbrown@tumblerings.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).