Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

How do you commit correctly?

(1/4) > >>

Pecan:
I want to commit a new cbKeyBinder.

Do you drag the new code to ...\trunk\src\plugins\contrib\keybinder
and commit from there? Or do you drag the .svn data to a clean directory
and commit from there?

Its been a long time since I used any CVS like pgms, and I wasn't good at
it even then. I don't want to screw anything up.

Just asking before doing...

thanks
pecan
 

Der Meister:
The normal procedure should be something like this:
1. Check out a working copy - 'svn checkout ...' or update an existing working copy - 'svn update'.
2. Make your changes to that working copy.
3. If your changes work, then do a 'svn commit' in the same directory where you did the 'svn checkout ...' (or 'svn update'). Thats all.

But note: This is a more general procedure. I can't say anything about special things here with Code::Blocks because I don't have write access to the repository. But I know no reason why anyone should ever go away form this procedure and use subversion in a different way.

thomas:
The best solution in the current situation would be to check out HEAD and replace the source files (but not the .svn folder!) with your new versions.

For the future, you should check out either a full working copy of Code::Blocks or you can just check out the plugin's subdirectory and work in that. Seriously, work on the checked out version, that's why you call it a working copy. You have a lot of advantages when doing so. Then just commit when you're done.

Alternatively, since you are the plugin's maintainer, you may want to make a separate project at BerliOS and check out your working copies from that repository (and only commit to that repository, too). This again is easier for you, and it has a lot of advantages too (and no disadvantages at all).

Pecan:
Ok, so I took my cbGet.cmd file and changed the "checkout" option to
"commit". But I get the following msg. Could someone point my
nose in the right direction??


--- Code: ---C:\Usr\Proj\cbBeta>cd trunk

C:\Usr\Proj\cbBeta\trunk>..\cbcommit

C:\Usr\Proj\cbBeta\trunk>PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32
\Wbem;\c:\usr\bin;c:\usr\bin\subversion\bin

C:\Usr\Proj\cbBeta\trunk>SET APR_ICONV_PATH=C:\usr\bin\Subversion\iconv

C:\Usr\Proj\cbBeta\trunk>svn --username {myname} --password {mypswd} commit svn:/
/svn.berlios.de/codeblocks/trunk
svn: Can't check path 'svn:\\svn.berlios.de\codeblocks\trunk': The filename, dir
ectory name, or volume label syntax is incorrect.

C:\Usr\Proj\cbBeta\trunk>

--- End code ---

thanks
pecan

takeshimiya:
Can it be:

Because TortoiseSVN is a Windows Shell Extension, it is not able to use the notion of a current working directory. All working copy paths must be given using the absolute path, not a relative path.

?

Navigation

[0] Message Index

[#] Next page