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 restor
On 3/19/08, Ulrich Telle <[EMAIL PROTECTED]> 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 Fr
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
...
On 3/18/08, Ulrich Telle <[EMAIL PROTECTED]> 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
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 end
Luciano Cattani ha scritto:
> Hi,
> there is no problem for me to loose the CVS's history
> of my component:
>
> wxJSON
done!
Francesco
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual
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
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, probab
--- Francesco Montorsi <[EMAIL PROTECTED]> 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 w
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
-
This SF.net email is sponsored by: Microsoft
Defy all ch
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 SV
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
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 f
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 holdout
14 matches
Mail list logo
