From: "Stefan Pfetzing" <stefan.pfetzing@gmail.com>
To: git <git@vger.kernel.org>
Subject: Re: Re: Moving a directory into another fails
Date: Mon, 4 Dec 2006 19:19:58 +0100 [thread overview]
Message-ID: <f3d7535d0612041019q4bda01a1k9938b056d51f8a78@mail.gmail.com> (raw)
In-Reply-To: <20060728014350.GI13776@pasky.or.cz>
Hi Folks,
2006/7/28, Petr Baudis <pasky@suse.cz>:
> > mv: cannot stat `"gitweb/test/M\\303\\244rchen"': No such file or directory
since when is this file in the official git.git tree?
Its quite problematic when used on HFS+ because it uses UTF-16 internally IMHO.
Git always thinks there is a new file in my git.git clone.
--- snip ---
dreamind@paris:~/src/git% git status
# Untracked files:
# (use "git add" to add to commit)
#
# gitweb/test/MaÌrchen
nothing to commit
--- snap ---
bye
dreamind
--
http://www.dreamind.de/
next prev parent reply other threads:[~2006-12-04 18:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 15:00 Moving a directory into another fails Jon Smirl
2006-07-26 22:34 ` Nicolas Vilz
2006-07-26 23:03 ` Jon Smirl
2006-07-26 23:25 ` Nicolas Vilz
2006-07-28 1:43 ` Petr Baudis
2006-12-04 18:19 ` Stefan Pfetzing [this message]
2006-12-04 18:56 ` Jakub Narebski
2006-12-04 19:03 ` Johannes Schindelin
2006-12-04 19:10 ` Jakub Narebski
2006-12-04 19:10 ` Johannes Schindelin
2006-12-04 19:37 ` Jakub Narebski
[not found] ` <7617FA7E-D49A-4A4C-B033-C2CB20623F5F@wf227.com>
2006-12-04 21:01 ` Johannes Schindelin
2006-12-04 20:26 ` Linus Torvalds
2006-12-04 20:51 ` Linus Torvalds
2006-12-04 20:54 ` Shawn Pearce
2006-12-04 20:56 ` Jakub Narebski
2006-12-04 21:05 ` Johannes Schindelin
2006-12-04 21:23 ` Linus Torvalds
2006-12-05 7:34 ` Johannes Schindelin
2006-12-05 9:36 ` Jakub Narebski
2006-12-05 14:11 ` filesystem encodings and gitweb tests, was " Johannes Schindelin
2006-12-05 14:29 ` Jakub Narebski
2006-12-05 14:40 ` Johannes Schindelin
2006-12-05 17:11 ` Linus Torvalds
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=f3d7535d0612041019q4bda01a1k9938b056d51f8a78@mail.gmail.com \
--to=stefan.pfetzing@gmail.com \
--cc=git@vger.kernel.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).