svn command --cl don't support names that contain chinese characters.
E,g. command “svn status -q D:\Project”, we see there is a changelist
named “好”, but when use command “svn status -q --verbose D:\Project
--ignore-externals --cl 好”, there is nothing to print.
Bluce Lu bluc...@51buy.com writes:
svn command --cl don't support names that contain chinese characters.
E,g. command “svn status -q D:\Project”, we see there is a changelist
named “好”, but when use command “svn status -q --verbose D:\Project
--ignore-externals --cl 好”, there is nothing to
On 04/25/2013 05:14 AM, Philip Martin wrote:
Bluce Lu bluc...@51buy.com writes:
svn command --cl don't support names that contain chinese characters.
E,g. command “svn status -q D:\Project”, we see there is a changelist
named “好”, but when use command “svn status -q --verbose D:\Project
I used tortoise svn to create changelist 好. :)
-邮件原件-
发件人: C. Michael Pilato [mailto:cmpil...@collab.net]
发送时间: 2013年4月25日 20:18
收件人: Philip Martin
抄送: Bluce Lu; users@subversion.apache.org
主题: Re: svn command --cl don't support names that contain chinese characters.
On 04/25/2013 05:14
On 04/25/2013 08:31 AM, Philip Martin wrote:
Yes, I was using UTF-8. I see the bug in iso-8859-1:
$ svn cl å wc/f
A [å] wc/f
$ svn st wc
--- Changelist 'å':
wc/f
$ svn st --cl å wc
$
With your patch:
$ svn st --cl å wc
--- Changelist 'å':
wc/f
Committed my
On Thu, Apr 25, 2013 at 08:37:01AM -0400, C. Michael Pilato wrote:
Committed my patch:
... which means the fix will likely be released in 1.7.10 and 1.8.0-alpha1 (or
1.8.0-rc1). The fix does not affect tortoisesvn; if it exhibits a problem,
contact the tortoisesvn developers at
On 04/24/2013 08:52 PM, C. Michael Pilato wrote:
The closest thing to official would be the Version Control With Subversion
book (http://svnbook.org/). But don't expect to find an ordered list of
steps to setting up a Subversion server, because that's just not the
audience for that text.
It
On 04/25/2013 09:00 AM, Zé wrote:
On 04/24/2013 08:52 PM, C. Michael Pilato wrote:
The closest thing to official would be the Version Control With Subversion
book (http://svnbook.org/). But don't expect to find an ordered list of
steps to setting up a Subversion server, because that's just
Daniel Shahaf danie...@apache.org writes:
On Thu, Apr 25, 2013 at 08:37:01AM -0400, C. Michael Pilato wrote:
Committed my patch:
... which means the fix will likely be released in 1.7.10 and 1.8.0-alpha1 (or
1.8.0-rc1). The fix does not affect tortoisesvn; if it exhibits a problem,
contact
Philip Martin wrote on Thu, Apr 25, 2013 at 15:19:45 +0100:
Daniel Shahaf danie...@apache.org writes:
On Thu, Apr 25, 2013 at 08:37:01AM -0400, C. Michael Pilato wrote:
Committed my patch:
... which means the fix will likely be released in 1.7.10 and 1.8.0-alpha1
(or
1.8.0-rc1).
I am certain there is simple way out of this situation.
Some files were committed to trunk which have incorrect updates.
What's the easiest way to roll back to the previous versions (before the
erroneous changes were committed)?
Should I checkout the previous revision and commit them over the
On Thu, Apr 25, 2013 at 3:34 PM, C M cmanalys...@gmail.com wrote:
I am certain there is simple way out of this situation.
Some files were committed to trunk which have incorrect updates.
What's the easiest way to roll back to the previous versions (before the
erroneous changes were
On Thu, Apr 25, 2013 at 2:34 PM, C M cmanalys...@gmail.com wrote:
I am certain there is simple way out of this situation.
Some files were committed to trunk which have incorrect updates.
What's the easiest way to roll back to the previous versions (before the
erroneous changes were
C M wrote:
Some files were committed to trunk which have incorrect updates.
What's the easiest way to roll back to the previous versions (before the
erroneous changes were committed)?
another way is to delete the trunk and reestablish it by copying the
last correct trunk revision.
This way a
14 matches
Mail list logo