Menu
▾
▴
wxcode-users
|
From: John L. <jla...@gm...> - 2008-03-17 02:45:33
|
A while back a number of components switched to SVN from CVS and I and a few others were a little hesitant. However, since then, wxWidgets itself now uses SVN and has for months. I have not heard that anyone regrets their decision and so I think maybe it's time to ask again if there are any holdouts for CVS? My components are: wxplotctrl wxsheet wxstedit wxthings wxvidcap I found this rather ugly method to convert to SVN on the web http://www.xs4all.nl/~carlo17/svn/cvs2svn.html Francesco, I think you had mentioned that you had a script to convert components to SVN? Could you convert mine or make the script available? (I also want to do wxLua) Thanks, John |
|
From: Angelo M. <ama...@gm...> - 2008-03-17 05:07:04
|
I would like to see all of the wx projects using SVN. Being a developer who was once comfortable with RCS, then CSV, I can honestly say once you've used Subversion (SVN) a few times, you'll "get it" as far as why SVN is replacing CSV. I will admit though, if you have a CSV/RCS mindset, you will find SVN hard to grasp at first. --angelo On Sun, Mar 16, 2008 at 10:45 PM, John Labenski <jla...@gm...> wrote: > A while back a number of components switched to SVN from CVS and I and > a few others were a little hesitant. However, since then, wxWidgets > itself now uses SVN and has for months. I have not heard that anyone > regrets their decision and so I think maybe it's time to ask again if > there are any holdouts for CVS? > > My components are: > wxplotctrl > wxsheet > wxstedit > wxthings > wxvidcap > > > I found this rather ugly method to convert to SVN on the web > http://www.xs4all.nl/~carlo17/svn/cvs2svn.html<http://www.xs4all.nl/%7Ecarlo17/svn/cvs2svn.html> > > Francesco, I think you had mentioned that you had a script to convert > components to SVN? Could you convert mine or make the script > available? (I also want to do wxLua) > > Thanks, > John > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > |
|
From: Francesco M. <f18...@ya...> - 2008-03-17 14:43:04
|
John Labenski ha scritto: > A while back a number of components switched to SVN from CVS and I and > a few others were a little hesitant. However, since then, wxWidgets > itself now uses SVN and has for months. I have not heard that anyone > regrets their decision and so I think maybe it's time to ask again if > there are any holdouts for CVS? I don't think there's any... SVN for wxCode is perfectly integrated just as CVS. The only drawback of (wxCode) SVN respect CVS it is that any developer may write everywhere (see http://sourceforge.net/tracker/index.php?func=detail&aid=1614921&group_id=1&atid=350001)... but this never happened so far. > My components are: > wxplotctrl > wxsheet > wxstedit > wxthings > wxvidcap > > I found this rather ugly method to convert to SVN on the web > http://www.xs4all.nl/~carlo17/svn/cvs2svn.html > > Francesco, I think you had mentioned that you had a script to convert > components to SVN? ehmm, honestly not: IIRC the last time I read the SF docs about SVN, it wasn't possible in wxCode context to "move" components retaining their history. I.e. I simply added my components (and others for the people which asked it to me) to SVN as new stuff. This is unconvenient as it means I must go in the viewVC part dedicated to CVS to browse the history of my components before the move to SVN but fortunately I almost never need to do it (I prefer to put warnings/notes in my sources rather in the component history's comments). > Could you convert mine or make the script > available? (I also want to do wxLua) for wxLua we can do a conversion without losing any history information simply using the SF web interface (which internally uses svnadmin) but for wxCode components unfortunately we can't (AFAIK)... If you're ok with having your component history partially in CVS and partially in SVN I can add them to SVN... Francesco |
|
From: Ulrich T. <ulr...@gm...> - 2008-03-17 17:01:20
|
Hi Francesco, >> ... components switched to SVN from CVS ... >> ... since then, wxWidgets itself now uses SVN ... > I don't think there's any... SVN for wxCode is perfectly integrated just as CVS Although I don't have much experience with SVN I would agree to move my components from CVS to SVN. > If you're ok with having your component history partially in CVS and > partially in SVN I can add them to SVN... This would not impose a problem for me. So I'd like to ask you for adding my components wxsqlite3 wxpdfdoc to SVN. Thanks. Regards, Ulrich |
|
From: Francesco M. <f18...@ya...> - 2008-03-18 19:20:07
|
Ulrich Telle ha scritto: > Hi Francesco, > >>> ... components switched to SVN from CVS ... >>> ... since then, wxWidgets itself now uses SVN ... >> I don't think there's any... SVN for wxCode is perfectly integrated just as CVS > > Although I don't have much experience with SVN I would agree to move my > components from CVS to SVN. > >> If you're ok with having your component history partially in CVS and >> partially in SVN I can add them to SVN... > > This would not impose a problem for me. So I'd like to ask you for > adding my components > > wxsqlite3 > wxpdfdoc > > to SVN. Thanks. done! Francesco |
|
From: Casey O'D. <cas...@gm...> - 2008-03-17 17:51:34
|
I'm happy to have wxCurl move over to SVN. Even if we leave the current history in CVS, I think the benefits of SVN are enough to warrant the change over. Best. Casey |
|
From: Francesco M. <f18...@ya...> - 2008-03-18 19:15:41
|
Casey O'Donnell ha scritto: > I'm happy to have wxCurl move over to SVN. actually wxCurl is already in wxCode SVN :) I'd really like to make the first release but I never managed to fix that Unicode/ANSI problem; also since this is a thing which deeply changed in new wx3 / upcoming wx2.9, probably it's worth doing the release once 2.9.0 is out and make it compatible with wx >= 2.9 Francesco |
|
From: Luciano C. <lu...@ma...> - 2008-03-18 13:05:40
|
--- Francesco Montorsi <f18...@ya...> ha
scritto:
> ... SVN for wxCode is perfectly integrated just
> as CVS. The only drawback of (wxCode) SVN respect
> CVS it is that any
> developer may write everywhere
> ... IIRC the last time I read the SF
> docs about SVN, it
> wasn't possible in wxCode context to "move"
> components retaining their
> history. I.e. I simply added my components (and
> others for the people
> which asked it to me) to SVN as new stuff.
>
>
> Francesco
>
Hi,
there is no problem for me to loose the CVS's history
of my component:
wxJSON
Francesco, can you please move it to SVN?
Luciano
Inviato da Yahoo! Mail.
Il servizio di posta con lo spazio illimitato.
http://it.docs.yahoo.com/mail/overview/index.html
|
|
From: Francesco M. <f18...@ya...> - 2008-03-18 19:25:15
|
Luciano Cattani ha scritto: > Hi, > there is no problem for me to loose the CVS's history > of my component: > > wxJSON done! Francesco |
|
From: Bryan P. <br...@ib...> - 2008-03-19 00:21:07
|
On 3/18/08, Ulrich Telle <ulr...@gm...> wrote: > As I'm quite new to SVN I need a bit of advice. As you know I work > mainly on a Windows platform. Although I enabled native line endings in > the TortoiseSVN settings I got all my source files with Unix line > endings when I checked out my wxCode components. How can I accomplish to > get Windows line endings? What happens, when I add new files having > Windows line endings? Are they converted correctly when committed to SVN? When you say that you "enabled native line endings in TortoiseSVN", what exactly do you mean? You will need to set the "svn:eol-style" property on all files that you want to change the behavior for. You can setup TortoiseSVN to set that property by default on all files of certain kinds, but it won't set those properties if the file already exists in SVN. You'll need to add the property to those files by hand. Regards, Bryan Petty |
|
From: Bryan P. <br...@ib...> - 2008-03-19 06:42:09
|
On 3/19/08, Ulrich Telle <ulr...@gm...> wrote: > > enable-auto-props = yes > > [auto-props] > *.c = svn:eol-style=native > *.cpp = svn:eol-style=native > *.h = svn:eol-style=native > ... Yes, this should add that property to those files automatically when you 'svn add' them. > Since Francesco moved the files from CVS to SVN, all files exist already > in SVN. Where do I have to set the property? I tried to add the property > manually for one source file, but the line ending did not change. It might be possible that you'll need to delete your files, and check them out again in order for the change to be evident on your machine. I don't think TortoiseSVN (or SVN itself) would modify your existing files. Regards, Bryan Petty |
|
From: Ulrich T. <ulr...@gm...> - 2008-03-19 07:42:18
|
Bryan Petty schrieb: > It might be possible that you'll need to delete your files, and check > them out again in order for the change to be evident on your machine. > I don't think TortoiseSVN (or SVN itself) would modify your existing > files. Yes, deleting the files in my working copy and restoring them via SVN update did the trick. Thanks a lot! Regards, Ulrich |
|
From: Ulrich T. <ulr...@gm...> - 2008-03-18 21:40:49
|
Hi Francesco, Francesco Montorsi schrieb: >> ... So I'd like to ask you for adding my components >> >> wxsqlite3 >> wxpdfdoc >> >> to SVN. Thanks. > done! Thanks. As I'm quite new to SVN I need a bit of advice. As you know I work mainly on a Windows platform. Although I enabled native line endings in the TortoiseSVN settings I got all my source files with Unix line endings when I checked out my wxCode components. How can I accomplish to get Windows line endings? What happens, when I add new files having Windows line endings? Are they converted correctly when committed to SVN? Regards, Ulrich |
|
From: Ulrich T. <ulr...@gm...> - 2008-03-19 06:05:49
|
Bryan Petty schrieb: > When you say that you "enabled native line endings in TortoiseSVN", > what exactly do you mean? I added/activated the following lines in TortoiseSVN: enable-auto-props = yes [auto-props] *.c = svn:eol-style=native *.cpp = svn:eol-style=native *.h = svn:eol-style=native ... > You will need to set the "svn:eol-style" property on all files that > you want to change the behavior for. You can setup TortoiseSVN to set > that property by default on all files of certain kinds, but it won't > set those properties if the file already exists in SVN. You'll need to > add the property to those files by hand. Since Francesco moved the files from CVS to SVN, all files exist already in SVN. Where do I have to set the property? I tried to add the property manually for one source file, but the line ending did not change. Regards, Ulrich |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X