1. svn Q: How do you put files in a sourceforge project?

I have this much done. The question is how to put files in this project.

https://sourceforge.net/projects/dmak/

The book svn-book.pdf is as clear as mud to me. I did Google searches to find a clue but everything is as clear as mud to me. I tried 'svn import' a bunch of different ways but that didn't do anything. 'svn checkout' seemed to work but of course there is nothing to check out at this time.

I gotta either learn how to get started with svn or else remove the project from sourceforge and find a different home for it.

new topic     » topic index » view message » categorize

2. Re: svn Q: How do you put files in a sourceforge project?

Jerry_Story said...

I have this much done. The question is how to put files in this project.

https://sourceforge.net/projects/dmak/

The book svn-book.pdf is as clear as mud to me. I did Google searches to find a clue but everything is as clear as mud to me. I tried 'svn import' a bunch of different ways but that didn't do anything. 'svn checkout' seemed to work but of course there is nothing to check out at this time.

I gotta either learn how to get started with svn or else remove the project from sourceforge and find a different home for it.

If you've done a checkout, then you've got a working copy. Move your files there, and let svn know about them using add:

  $ svn add * 
This will tell svn that the next commit should send these files. Try using the status command to see the changes since checkout:
  $ svn st 
Then, when you're ready go ahead and commit:
  $ svn ci -m "initial import of files" 
Note that 'ci' is the abbreviation for commit, and -m is for your commit message. If you set the environment variable SVN_EDITOR, you can write the message in whatever editor you specify. I have SVN_EDITOR set to nano, for instance.

Finally, update your working copy:

  $ svn up 
In general, update (up), status (st) and commit (ci) will account for the vast majority of your svn usage.

Matt

new topic     » goto parent     » topic index » view message » categorize

3. Re: svn Q: How do you put files in a sourceforge project?

About putting my files in my working copy.

This is what I have in what I'm guessing is the working copy.
I have directory svn. Inside this is directory /dmak. Inside svn/dmak I have directories /conf, /db, /hooks, /locks, /format, and a file called 'README.txt'.

How should I put my files in svn/dmak? (assuming that this is the working directory) Should they be in svn/dmak/trunk?

The files to go into the working directory are in upload_dmak/dmak. This consists of a bunch of subdirectories and a bunch of files. Should I put all this stuff in svn/dmak/trunk?

I'm totally green about svn. Maybe some day it will seem easy, but for now I need to ask ignorant questions.

new topic     » goto parent     » topic index » view message » categorize

4. Re: svn Q: How do you put files in a sourceforge project?

Jerry,

I would really recommend reading the book "Version Control with Subversion". It can be had online at:

http://svnbook.red-bean.com/

I believe the Chapter 2, Basic Usage, will get you going pretty strong with it.

Jeremy

new topic     » goto parent     » topic index » view message » categorize

5. Re: svn Q: How do you put files in a sourceforge project?

For the users that want to use SVN commands on Linux.
Since there is no TortoiseSVN for linux I just wanted to
let you know there is an add on MENU for Firefox that will
make using the SVN commands a little easier on Linux.
Here is the link :

https://addons.mozilla.org/en-US/firefox/addon/3416

new topic     » goto parent     » topic index » view message » categorize

6. Re: svn Q: How do you put files in a sourceforge project?

mattlewis said...
Jerry_Story said...

I have this much done. The question is how to put files in this project.

https://sourceforge.net/projects/dmak/

The book svn-book.pdf is as clear as mud to me. I did Google searches to find a clue but everything is as clear as mud to me. I tried 'svn import' a bunch of different ways but that didn't do anything. 'svn checkout' seemed to work but of course there is nothing to check out at this time.

I gotta either learn how to get started with svn or else remove the project from sourceforge and find a different home for it.

If you've done a checkout, then you've got a working copy. Move your files there, and let svn know about them using add:

  $ svn add * 
This will tell svn that the next commit should send these files. Try using the status command to see the changes since checkout:
  $ svn st 
Then, when you're ready go ahead and commit:
  $ svn ci -m "initial import of files" 
Note that 'ci' is the abbreviation for commit, and -m is for your commit message. If you set the environment variable SVN_EDITOR, you can write the message in whatever editor you specify. I have SVN_EDITOR set to nano, for instance.

Finally, update your working copy:

  $ svn up 
In general, update (up), status (st) and commit (ci) will account for the vast majority of your svn usage.

Matt

Thanks. I have your message bookmarked for reference.

I got the files on there now. http://dmak.svn.sourceforge.net/

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu