On Fri, 13 Jan 2012 21:00:01 +0100, <[email protected]> wrote:
Don't try to create the "c" directory, it will just confuse things.
See here:
*wimpslot -min 8000k
*ram
*svnadmin create repos
*cdir workdir
*cdir workdir.c
*echo Test { > workdir.c.testfile }
*settype workdir.c.testfile fff
*svn co file:///ram:$/repos workdir
Checked out revision 0.
*svn add workdir/testfile.c
A workdir/testfile.c
*svn ci workdir/testfile.c
Press R to return data, A to abort
Adding workdir/testfile.c
Transmitting file data .
Committed revision 1.
*svn co file:///ram:$/repos workdir2
A workdir2/testfile.c
Checked out revision 1.
*type workdir2.c.testfile
Test
*svn list file:///ram:$/repos
testfile.c
Hope this helps.
Cheers,
Jan-Jaap
Thanks for the detailed response, Jan-Jaap.
Does this mean that no one who uses !SVN on RISC OS also uses the
traditional layout of directories for C coding?
You have (shock, horror ;) all .c and .h files in the same directory?
Not that I'm conservative, traditionalist or just plain stubborn or
anything (honest), but is there no way around this?
Cheers,
WPB
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
