[C.CC USERS] having trouble committing files to /community directory

Jon Simpson me at jonsimpson.co.uk
Fri May 7 20:17:03 BST 2010


Hi Aaron,

On Fri, May 7, 2010 at 8:01 PM, Aaron Ryan <amrphoto1 at gmail.com> wrote:
> Martin and Jon,
>
> So, here's what i've done thus far:
>
> I checked out the directory:
> https://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/trunk/tvm/arduino/community/bringfire/
>
> I put the files that i want to upload into the local svn directory on my
> hard drive: /home/aaron/bringfire
>
> I "cd" into /home/aaron/bringfire in the terminal.
>
> First I ran:
> svn commit -m /home/aaron/bringfire/led-chase-files
>  and received the log error message quoted in last email.

You should ensure that whatever you want to add to the repository is
added to subversion - just having the files in the right directory
wont mean SVN adds them to the list of version controlled files. SVN
keeps its own list of which files and directories it knows about.

'svn status' will let you see what the status of your files is - if
its a question mark, the files aren't added - you can add them with
'svn add filename', where filename can be a wildcard specifier (*.c,
*.occ, etc...) or an actual directory or file (directories are
recursively added!)

Once you can see files with an 'A' status (i.e. ready to add) in your
svn status output, you can say svn commit to open an editor (as you've
already encountered) - usually you'll add a one line comment about
what you've changed on the top line - don't remove any of the existing
contents. When you save the file and quit the editor, the commit
happens.

All of this is covered in the book in much better detail - that basic
workflow link isn't too sizable and it's well worth getting your head
around SVN as some of its suggestions when things go wrong are very
bad ideas. (a lot of the --force-blah options are usually not what you
should do).

Cheers,
Jon




More information about the users mailing list