From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Re: Moving a directory into another fails
Date: Mon, 04 Dec 2006 20:10:12 +0100 [thread overview]
Message-ID: <el1rmm$bca$2@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0612042001320.28348@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Mon, 4 Dec 2006, Jakub Narebski wrote:
>
>> [...] git should acquire core.filesystemEncoding configuration variable
>> which would encode from filesystem encoding used in working directory
>> and perhaps index to UTF-8 encoding used in repository (in tree objects)
>> and perhaps index.
>
> So, you want to pull in all thinkable encodings? Of course, you could rely
> on libiconv, adding yet another dependency to git. (Yes, I know, mailinfo
> uses it already. But I never use mailinfo, so I do not need libiconv.)
A conditional dependency. If you don't have libiconv, this feature wouldn't
be available.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-04 19:08 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 [this message]
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='el1rmm$bca$2@sea.gmane.org' \
--to=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.