From: Jay Soffian <jaysoffian@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Teemu Likonen <tlikonen@iki.fi>, git@vger.kernel.org
Subject: Re: non-ascii filenames issue
Date: Sun, 5 Apr 2009 12:23:35 -0400 [thread overview]
Message-ID: <76718490904050923j105e383dsf650afa0a0687858@mail.gmail.com> (raw)
In-Reply-To: <43d8ce650904050351p72590d52l8861b3901f95201a@mail.gmail.com>
On Sun, Apr 5, 2009 at 6:51 AM, John Tapsell <johnflux@gmail.com> wrote:
> Unfortunately not, because for some absolutely crazy reason
Bzzt. http://article.gmane.org/gmane.comp.version-control.git/50830
And, as always, patches welcomed.
j.
next prev parent reply other threads:[~2009-04-05 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:36 non-ascii filenames issue Gregory Petrosyan
2009-04-05 9:54 ` Teemu Likonen
2009-04-05 10:01 ` Gregory Petrosyan
2009-04-05 10:51 ` John Tapsell
2009-04-05 16:23 ` Jay Soffian [this message]
2009-04-05 19:29 ` Junio C Hamano
2009-04-05 20:22 ` Jay Soffian
2009-04-06 7:28 ` Peter Krefting
2009-04-06 9:12 ` Johannes Schindelin
2009-04-06 22:33 ` Dmitry Potapov
2009-04-07 8:26 ` demerphq
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=76718490904050923j105e383dsf650afa0a0687858@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=tlikonen@iki.fi \
/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).