[cvsnt] Re: loginfo problem with brances and files with embedded spaces....

Bo Berglund bo.berglund at telia.com
Sun Nov 17 23:47:20 GMT 2002


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Tony,
you don't have to rush things. I found a workaround so I can properly
handle the 'spacey' files in the loginfo processing. Still confusing
though, but if people stop using files with spaces in them all would
be OK...
Next test: What will happen if I add a submodule with a folder name
containing spaces...

Cheers,
Bo

On Sun, 17 Nov 2002 22:51:06 +0100, Bo Berglund
<bo.berglund at telia.com> wrote:

>Tony,
>while testing the admin scripts (especially the taginfo) on the latest
>CVSNT build (with tagged files on StdIn) I ran into a real problem...
>Scenario:
> - A module containing files both with and without spaces.
> - The module is moved to a branch (BranchTest)
> - Two files are modified and committed, one contains spaces in name
>
>Problem:
>When loginfo executes the following information is obtained:
>Command line parameter #4 (in my case because I entered 3 others):
>TestModule/doc Test\ File.txt,1.5,1.5.2.1 Readme.txt,1.2,1.2.2.1
>On standard input:
>Update of C:/CVSREPO/test/TestModule/doc
>In directory: Welebobe:C:\CVSTEMP\cvs-serv3168
>
>Modified Files:
>      Tag: BranchTest
>        Test File.txt Readme.txt
>Log Message:
>Testing branch behaviour
>
>What this all boils down to is that I see no way to retrieve the
>actual list of file names from the StdIn data, yet I must do so
>because there is the only place I can find out which branch these
>files are on.
>For files without spaces in the name it works fine, I scan the StdIn
>and make a list of files for each tag. Then I really use the files on
>the command line to parse out revisions and stuff. Here the space
>escape is done so I can positively define where the file name is
>located and where the new file starts (after the space).
>
>How can I get the branch info off the StdIn???
>I can only see one solution and that is for CVSNT to escape the
>embedded spaces also in the StdIn message.
>I can really not even think of using some 'knowledge' from the command
>line, because there may in fact be files named very similarly, like:
>"File with spaces in name.txt"
>"File"
>"name.txt"
>"Spaces in name.txt"
>etc.
>
>Where can I put code to escape the embedded spaces in CVSNT?
>(As you probably know by now I am a C++ illiterate :-( )
>I like the StdIn message concerning the files to read:
>Modified Files:
>      Tag: BranchTest
>        Test\ File.txt Readme.txt
>
>
>
>/Bo
>(Bo Berglund, developer in Sweden)


/Bo
(Bo Berglund, developer in Sweden)



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook