From: Rogan Dawes <lists@dawes.za.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn and renames
Date: Thu, 12 Jul 2007 18:51:09 +0200 [thread overview]
Message-ID: <46965BFD.5080702@dawes.za.net> (raw)
In-Reply-To: <20070712090635.GA18155@mayonaise>
Eric Wong wrote:
>> I've personally noted a rename issue with committing funky characters
>> "#{}" in filenames (I was renaming to get rid of those funky characters of
>> course). Haven't had proper time to look into it.
>>
>> Did any previous successful commits have renames in them? You may want
>> to set similarity to 100% to disable rename detection.
>
> SVN over HTTP is most definitely behaves differently from svn:// and
> file:// wrt strange file names. I'll see if I can work on this again in
> day or two, or if anybody wants to pick up where I left off, my
> work-in-progress test case is below (it's currently failing, of course).
>
> I'll have to look into how (if) svk handles it and also at the svn
> command-line client. I'm fairly sure the command-line svn client
> handles it somehow...
>
> Right now I'm getting sleepy, my vision is blurring and I'm seeing
> "SVN" as "S/M" through my tired eyes...
>
Hi Eric,
This doesn't seem to be my problem. In my case, the filenames are quite
simple and straightforward.
Thanks
Rogan
next prev parent reply other threads:[~2007-07-12 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 13:11 git-svn and renames Rogan Dawes
2007-07-10 13:20 ` David Kastrup
2007-07-10 14:18 ` Rogan Dawes
2007-07-10 13:42 ` Florian Weimer
2007-07-10 14:01 ` Rogan Dawes
2007-07-11 8:20 ` Eric Wong
2007-07-12 9:06 ` Eric Wong
2007-07-12 16:51 ` Rogan Dawes [this message]
2007-07-16 4:53 ` [PATCH] git-svn: fix commiting renames over DAV with funky file names Eric Wong
2007-07-16 6:36 ` Rogan Dawes
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=46965BFD.5080702@dawes.za.net \
--to=lists@dawes.za.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.