headers
Olly Betts | 1 Dec 2006 02:23
Favicon
Gravatar

Re: Subversion migration - update

On 2006-11-30, William S Fulton <wsf <at> fultondesigns.co.uk> wrote:
> To be honest, I'd rather just get on with it.

Me too - this has dragged on for quite a while already.

> If it goes horribly wrong, and we'll know about it after just one or
> two commits, then we can just revert.

And because all files committed in a single operation get the same repo
version, it would be easy to pull out a patche for each commit to SVN
since the conversion, and then we can apply these to the CVS repo and
continue with that until we've resolved whatever the issue is.

> Maybe those with experience of converting over to svn can let us know
> whether it went smoothly and easily or not.

Doing the actual repo conversion was easy, but John's taking care of
that for us anyway (thanks John!)

Forcing my fingers to type "svn" instead of "cvs" took a while - I found
this harder than adapting to the small changes in the commands you use
for certain things (for example, "cvs -nq up" -> "svn status").  Most of
the common commands are the same - "cvs up" -> "svn up"; "cvs diff" ->
"svn diff".

I do find diffing against a tag or branch with SVN a bit more
complicated (though I suspect once I've had to do it more than a handful
of times it'll start to come naturally).  On the plus side, there aren't
the odd limitations with such diffing that CVS seems to have - I never
worked out how to diff between two dates on a branch with CVS without
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brad Watson | 1 Dec 2006 03:18
Picon
Favicon

Contributing (or not) ?

Greetings,

I've been working on a language module for GNU Smalltalk.  Ive have a module based on clisp.cxx that is
functional.  Can I contribute this this to this project ?

Thank you kindly,

Brad Watson

 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Permalink | Reply | 1 comment |
headers
John Lenz | 1 Dec 2006 06:32
Picon
Favicon

Re: Subversion migration - update

William S Fulton wrote:
>> Upon further thought.  Why don't we take this kind of slow at first.   
>> I'd like to suggest the idea that we set up SVN as kind of a pilot  
>> project, but continue to use CVS for awhile until people get a chance  
>> to test SVN and make sure it works.   Then, once we're satisfied with  
>> that, we make the formal transition.  Presumably, this approach will  
>> require us to convert the CVS repository twice (since we're going to  
>> keep working while this is going on).  However, it doesn't sound like  
>> that's going to be a problem.  Thoughts?
>>
>>     
>
> To be honest, I'd rather just get on with it. If it goes horribly wrong,
> and we'll know about it after just one or two commits, then we can just
> revert. We can make a test directory for testing stuff out on for those
> who want to find their feet with subversion. But by all accounts there
> ain't much radically different for the basics if you are used to cvs.
> Maybe those with experience of converting over to svn can let us know
> whether it went smoothly and easily or not.
>   

Well, I use subversion every day, and it is great.  I know the mono
project converted to svn in as little as a day (they have over 400
committers too!)  The first time, they didn't pass the right options to
cvs2svn, but ran it again and had the svn up within the day.  KDE
converted, and they have over 1000 committers.  KDE took it a little
slower, though.  Also, most of the problems/issues people like Mono, KDE
and such had is configuring and setting up the server.  But sourceforge
has done all that work already: the server is set up, permissions for
everything is set up, the on disk format for the database is configured,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jason Stewart | 1 Dec 2006 07:22
Picon
Gravatar

Re: Subversion migration - update

Hey all,

On 12/1/06, David Beazley <dave-swig <at> dabeaz.com> wrote:
>
> > To be honest, I'd rather just get on with it. If it goes horribly
> > wrong,

> My concern is that I don't want the universe to break and both CVS
> and SVN to be unavailable for weeks on end.

It won't break both. If for some reason the SVN dump is not what we
want, CVS will still be available read-only to make a better dump.

All of Apache Software Foundation switched to SVN, and there hasn't
been a single problem in the switchover - countless projects,
countless committers...

We should just get on with it...

As far as wanting some other VCS other than SVN: until it gets offered
by the SF admins as an alternative, we have a choice between CVS and
SVN. CVS is broken and SVN isn't. Once we've switched to SVN we can
still use other tools like svk on top of SVN.

Cheers, jas.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olly Betts | 1 Dec 2006 15:20
Favicon
Gravatar

Re: Subversion migration - update

On 2006-12-01, John Lenz <jlenz2 <at> math.uiuc.edu> wrote:
> With as few committers as we have, maintaining two source controls will
> just be too confusing and too much work.  Olly suggested exporting
> patches, but that doesn't work too well when you start moving files
> around in the svn... then we have to go in manually and do it.

You misunderstand me - I wasn't suggesting that we attempt to run the
two in parallel at all!

> We can convert, and leave the cvs around if something really breaks.

Exactly!

I was just pointing out that if after a week or two we discover some
reason why SVN isn't an improvement, it would be easy to take the
changes committed to SVN and apply them to the CVS tree in the same
commits used to apply them to SVN.  Then we could return to using CVS.

Not that I believe at all we'll regret moving, but Dave seems to be a
little nervous and I was trying to allay his fears.  I think it's better
we migrate now knowing there's an escape route than try to do an
experimental conversion.

Cheers,
    Olly

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Beazley | 1 Dec 2006 15:33

Re: Subversion migration - update

>
> Not that I believe at all we'll regret moving, but Dave seems to be a
> little nervous and I was trying to allay his fears.  I think it's  
> better
> we migrate now knowing there's an escape route than try to do an
> experimental conversion.

I'm not sure nervous is the right word.  I'm actually itching to  
start work on a number of SWIG-related things (documentation, etc.).   
Because of that, I would hate to see the CVS/SVN repository suddenly  
go wacko.    If John thinks he can do a conversion this weekend, I  
say go for it.   If there are things I need to do, let me know.

Cheers,
Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Dec 2006 15:41
Picon
Favicon

[ swig-Patches-1595567 ] (Java) Eliminate generation/use of explicit methods

Patches item #1595567, was opened at 2006-11-13 17:14
Message generated for change (Comment added) made by mr_amit
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301645&aid=1595567&group_id=1645

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
>Priority: 3
Private: No
Submitted By: Amit G Mendapara (mr_amit)
>Assigned to: William Fulton (wsfulton)
Summary: (Java) Eliminate generation/use of explicit methods

Initial Comment:
I have made some changes in java.cxx that eliminates 
generation/use of explicit methods.

The hack is that, an extra `basecall` flags is passed
to the JNI method. If the value of this flag is
JNI_TRUE, the JNI method will call the `base method`
otherwise will call the director version of the method.

- mr_amit <mr_amit <at> users.sourceforge.ner>

----------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marc Lepage | 1 Dec 2006 15:44

Re: Subversion migration - update

I've recently switched from being a cvs user to being an svn user. It's
pretty painless. Of course there's a bit of server setup to do, but if
SourceForge handles that, then it's done for you. (For setting up on a
personal machine, e.g. for home use, it's as simple as installing the
client tools and telling them to use a particular folder as a
repository.)

>From the perspective of actually using svn day to day, it's basically
the same as cvs (this is a stated goal of the project). I understand
branching/tagging is different, improved. It's very easy to move files
and directories around.

I had switched from using TortoiseCVS to TortoiseSVN on Windows. Those
tools are very similar also.

-----Original Message-----
From: swig-devel-bounces <at> lists.sourceforge.net
[mailto:swig-devel-bounces <at> lists.sourceforge.net] On Behalf Of David
Beazley
Sent: Friday, December 01, 2006 9:34 AM
To: Olly Betts
Cc: swig-devel <at> lists.sourceforge.net
Subject: Re: [Swig-devel] Subversion migration - update

>
> Not that I believe at all we'll regret moving, but Dave seems to be a
> little nervous and I was trying to allay his fears.  I think it's  
> better
> we migrate now knowing there's an escape route than try to do an
> experimental conversion.
(Continue reading)

Permalink | Reply | 17 comments |
headers
William S Fulton | 1 Dec 2006 21:02
Picon
Favicon
Gravatar

Re: Contributing (or not) ?

Brad Watson wrote:
> Greetings,
> 
> I've been working on a language module for GNU Smalltalk.  Ive have a module based on clisp.cxx that is
functional.  Can I contribute this this to this project ?
> 

Hi Brad

Smalltalk will be a welcome additional language, but there are a few
requirements before we can get you cvs commit access, or most likely
subversion access as you'll probably notice we are about to move over to
subversion. Check out the prerequisites here

http://www.swig.org/Doc1.3/Extending.html#Extending_prerequisites

and get back to us. One other thing is to format your code using the
make target in the Source directory. Use it like:

make beautify-file INDENTFILE=Modules/smalltalk.cxx

You might need to manually fix up a one or two quirky things it does,
but what it generates is basically the coding style we use.

William

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brad Watson | 2 Dec 2006 01:00
Picon
Favicon

Re: Contributing (or not) ?

Thanks William.  Ill check out those links and work on getting it into conformance.

Regards,

Brad

----- Original Message ----
From: William S Fulton <wsf <at> fultondesigns.co.uk>
To: Brad Watson <whitebearded1 <at> yahoo.com>
Cc: swig-devel <at> lists.sourceforge.net
Sent: Friday, December 1, 2006 12:02:44 PM
Subject: Re: [Swig-devel] Contributing (or not) ?

Brad Watson wrote:
> Greetings,
> 
> I've been working on a language module for GNU Smalltalk.  Ive have a module based on clisp.cxx that is
functional.  Can I contribute this this to this project ?
> 

Hi Brad

Smalltalk will be a welcome additional language, but there are a few
requirements before we can get you cvs commit access, or most likely
subversion access as you'll probably notice we are about to move over to
subversion. Check out the prerequisites here

http://www.swig.org/Doc1.3/Extending.html#Extending_prerequisites

and get back to us. One other thing is to format your code using the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane