As I announced earlier, Shorewall is transitioning from SVN to Git for SCM.
The first step was to create a Git repository from the SVN repository at Sourceforge. The second step was to upload the Git repository back to Sourceforge. I've been attempting to maintain both the SVN and Git repositories at Sourceforge in parallel and am finding that attempting to syncronize back and forth with updates to both SVN and to Git are problemmatic. In particular, syncronizing with SVN often backs out recent changes from my local repository! Rather than fight these problems, I'm going to simply stop updating trunk in the SVN repository at Sourceforge. All trunk development going forward will only be pushed to the Git repository. If you have a change that you want to include in trunk and you have not yet cloned the Git repository at SF (which is quite easy, BTW) send me a unified diff patch and I will apply the patch to my local tree and update Git. Thanks! -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
