Thanks! It works for me now!
another short question:
Do you know if there's a way to know what is the current tag I'm working
on? Meaning: If I want to use 'svn copy' on the file I'm working on now
without sending the argument of the source file but only the tag name, is
it possible to send the 'current file path' as the first argument?
For instance, if the user doesn't know on what tag he's working on,
assuming he's not working on the 'trunk' but rather on 'tag= Release_60'.
And now he wants to copy 'Release_60' to 'Release_61'. But he doesn't know
he's working on 'Release_60'. How do I find out using svn command lines?
If you look at my example I sent in the previous email, you can see I
filled in the argument= $target_path :
my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
But I'm looking for a way to fill it automatically with the "current
path/tag".
Is it possible?
Thanks a lot!
have a great day!
On Wed, Sep 12, 2012 at 12:10 PM, Tony Sweeney <tsweeney_at_omnifone.com>wrote:
> **
>
>
> ------------------------------
> *From:* Carmit Shiran [mailto:carmit.shiran_at_gmail.com]
> *Sent:* 12 September 2012 08:14
> *To:* Ryan Schmidt
> *Cc:* Cooke, Mark; users_at_subversion.apache.org
> *Subject:* Re: problem with dialog box uisng Tortoisesvn
>
> thanks for your help.
> Seems like I didn't have the whole svn package.
> I reinstalled the svn and made sure I pick the "command tool" and now the
> svn commands work for me.
>
> Though I have a problem with the tag command:
>
> I wrote a script in perl:
> my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> my $tag = "file:///C:/svn_repos3/tags/Release_63"
>
> system ("svn copy -m \"tagging the file\" \"$target_path\" \"$tag\" ");
>
> and got the following error:
>
> svn: E160005: Invalid control character '0X0a' in path 'Release_63\012'
>
> Does anyone know what this error is?
>
> That's just a line feed at the end of one of your variable strings. Use
> chomp to get rid of it and you should be golden.
>
> Tony.
>
> thanks!!
>
>
>
> On Wed, Sep 5, 2012 at 1:21 PM, Ryan Schmidt <
> subversion-2012c_at_ryandesign.com> wrote:
>
>>
>> On Sep 5, 2012, at 04:14, Carmit Shiran wrote:
>>
>> > c:\Program files\TortoiseSVN\bin> $svn commit
>> >
>> > I got the following message:
>> > '$svn' is not recognized as an internal or external command, operable
>> program or batch file.
>>
>> You're not supposed to type "$". We just use "$" to indicate "type the
>> things after this". It's a fairly common character for a command prompt.
>> This same convention is used by the SVN Book [1], which is a good document
>> to read to get familiar with how to use Subversion.
>>
>>
>> [1] http://svnbook.org/
>>
>>
>>
>>
>>
>>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5262 - Release Date: 09/11/12
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
Received on 2012-09-12 13:13:26 CEST