From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: sf <sf@b-i-t.de>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Non-ASCII paths and git-cvsserver
Date: Mon, 13 Nov 2006 15:22:46 -0300 [thread overview]
Message-ID: <46a038f90611131022l105b5df3ycdf7aa33016b336e@mail.gmail.com> (raw)
In-Reply-To: <45587A09.3020605@b-i-t.de>
On 11/13/06, sf <sf@b-i-t.de> wrote:
> Martin, are you sure your patch is needed? (see below)
Not 100% sure. I was just making sure we crossed all the Ts and dotted
the Is. I gather you have tried my patch and it didn't make any
difference. What SQLite and Perl versions are you using?
cheers,
next prev parent reply other threads:[~2006-11-13 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 11:11 Non-ASCII paths and git-cvsserver sf
2006-11-10 18:59 ` Martin Langhoff
2006-11-10 19:49 ` Junio C Hamano
2006-11-13 13:58 ` sf
2006-11-13 14:20 ` Jakub Narebski
2006-11-13 18:30 ` Robin Rosenberg
2006-11-13 18:57 ` Jakub Narebski
2006-11-13 21:41 ` Robin Rosenberg
2006-11-13 19:48 ` Junio C Hamano
2006-11-13 18:22 ` Martin Langhoff [this message]
2006-11-14 10:40 ` sf
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=46a038f90611131022l105b5df3ycdf7aa33016b336e@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=sf@b-i-t.de \
/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).