From: "Alexander Gladysh" <agladysh@gmail.com>
To: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Weird filename encoding issue
Date: Fri, 17 Oct 2008 11:59:20 +0400 [thread overview]
Message-ID: <c6c947f60810170059s3859d906r9935b5e80d8a41c6@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
Hi, all!
OS X 10.5.5 (English locale), Git 1.5.5.1
Windows XP SP2 (Russian), msysGit 1.5.6.1.1071.g76fb
[-- Attachment #2: Copy.zip --]
[-- Type: application/zip, Size: 116 bytes --]
next reply other threads:[~2008-10-17 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 7:59 Alexander Gladysh [this message]
2008-10-17 8:08 ` Weird filename encoding issue Alexander Gladysh
2008-10-17 8:55 ` Johannes Sixt
2008-10-18 2:58 ` Robin Rosenberg
2008-10-27 8:08 ` [msysGit] " Peter Krefting
2008-10-18 6:22 ` Alexander Gladysh
2008-10-18 9:35 ` [msysGit] " Robin Rosenberg
2008-10-18 17:51 ` Johannes Sixt
2008-10-19 14:11 ` [msysGit] " Alexander Gladysh
2008-10-17 8:57 ` Jakub Narebski
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=c6c947f60810170059s3859d906r9935b5e80d8a41c6@mail.gmail.com \
--to=agladysh@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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).