git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: Moving a directory into another fails
Date: Tue, 5 Dec 2006 10:36:13 +0100	[thread overview]
Message-ID: <200612051036.13645.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612050831550.28348@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

> On Mon, 4 Dec 2006, Linus Torvalds wrote:
> 
>> 	[core]
>> 		escapefilenames = true
> 
> I think this goes too far. The problem _only_ showed up with a made-up 
> test case for gitweb. Let's bite the apple when we _have_ to (which I 
> doubt will happen, because for the most part, developers understand that 
> spaces and umlauts have _no_ place in filenames, basically since UNIX was 
> invented by stupid US Americans who did not know anything about nice 
> filenames, let alone other languages than English and C).

No, the problem showed with stupid HFS+ which uses different encoding
for creating file, and different for readdir.

Perhaps we should remove gitweb/test directory, and move testing gitweb
to proper place, t/ directory. 

By the way, would it be correct to use external tools (if they exist),
namely HTMLtidy in gitweb output test to-be-written?
-- 
Jakub Narebski

  reply	other threads:[~2006-12-05  9:34 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
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 [this message]
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=200612051036.13645.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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).