• request_type: join-team --> new-doc

If there's a way to enable automatic email notification of SVN commits to a Beta Project, I haven't been able to find it. Can anyone enlighten me?

-- Joe Taylor (for the WSJT project)

Hello,

As a project admin, you should automatically get email notifications of code commits, if you're using the proper repository.

You actually used a classic SourceForge style repository instead of the SourceForge 2.0 Beta style repository for your project (your project is a SourceForge 2.0 Beta project). The repository you should be using is listed on this page: http://sourceforge.net/p/wsjt/code/

Once you start using the correct repository you should automatically get emails for each code commit.

For help with moving your code from the classic SourceForge repository to the SourceForge 2.0 Beta, see this workaround in our community docs: https://sourceforge.net/p/forge/community-docs/Subversion/

Regards,
Chris Tsai, SourceForge.net Support

PS. I've also logged a ticket with our engineering team to add a way to subscribe to code commits without being a project admin. See this ticket: http://sourceforge.net/p/allura/tickets/2922/

Hi Chris,

Many thanks for your replies to my query. I'm trying to follow your
workaround to move my code from the classic SourceForge repository
to the SourceForge 2.0 Beta.

Logged into a sourceforge shell, when I do this:

$ [k1jt,wsjt@shell-24004 ~]$ svnsync init --username k1jt \ svn+ssh://k1jt@svn.code.sf.net/p/wsjt/svn/ \ https://wsjt.svn.sourceforge.net/svnroot/wsjt/

I get this response:

$ svnsync: No repository found in
'svn+ssh://k1jt@svn.code.sf.net/p/wsjt/svn'

Evidently I must create the 2.0 Beta repository before I can import my
code to it. Makes sense... but how??

-- Joe

On 10/4/2011 12:26 PM, Christopher Tsai wrote:

Hello,

As a project admin, you should automatically get email notifications of
code commits, if you're using the proper repository.

You actually used a classic SourceForge style repository instead of the
SourceForge 2.0 Beta style repository for your project (your project is
a SourceForge 2.0 Beta project). The repository you /should/ be using is
listed on this page: http://sourceforge.net/p/wsjt/code/

Once you start using the correct repository you should automatically get
emails for each code commit.

For help with moving your code from the classic SourceForge repository
to the SourceForge 2.0 Beta, see this workaround in our community docs:
https://sourceforge.net/p/forge/community-docs/Subversion/

Regards,
Chris Tsai, SourceForge.net Support

PS. I've also logged a ticket with our engineering team to add a way to
subscribe to code commits without being a project admin. See this
ticket: http://sourceforge.net/p/allura/tickets/2922/

---

comm-docs-tickets:2 SVN help/tips and tricks

Status: open
Created: Thu Aug 04, 2011 09:03 PM UTC by Christopher Tsai
Last Updated: Sun Oct 02, 2011 02:51 PM UTC Owner: nobody

A general SVN doc would probably be useful. Some ideas for content:

1. A getting started type guide with some examples
2. Some links to recommended resources for digging deeper
3. Tips and Tricks
4. Any SF specific info (would probably be worth differentiating
   between classic projects and SF 2.0 Beta projects)

Click here to start this page
http://sourceforge.net/p/forge/community-docs/Subversion

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/forge/comm-docs-tickets/2/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/prefs/

The mountpoint for your repository is "code" not "svn" (as it was in my example), so you'll need to make that replacement as well:

$ svnsync init --username k1jt svn+ssh://k1jt@svn.code.sf.net/p/wsjt/code/ https://wsjt.svn.sourceforge.net/svnroot/wsjt/

Also note that for my example, I ran that from my local machine, not the shell service, though I suspect it should work there as well.

Chris --

Sorry to bother you a few minutes ago, I figured out how to remove the
repository lock.

"svnsync sync" is now chugging away... some 2400 revisions to go. :-)

Thanks again for your speedy and informative help!!

-- Joe Taylor