On 21.09.2006, at 07:29, Bernd Eidenschink wrote:
You have very tough requirements for your revision control system
and made
that very clear.
Ah, no.. tough it is not: simple to use, must do the job.
That isn't tough. It is just that I do not see any benefit.
Therefore I asked about what _i
> On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
> > If you have the client installed, simply try for a checkout:
> >
> > # svn co https://svn.sourceforge.net/svnroot/naviserver/trunk/
> > naviserver
>
> Simple? Simple???
[...]
>There you go. What is simple here? My (pessimistic, but close to
On 20.09.2006, at 21:36, Vlad Seryakov wrote:
In out simplest case no benefits because out repository structure does
not change often. It is just more modern source control thing, but we
can stay on CVS.
OK. More (or less) modern, I do not care. It has to do the job
and be reasonably simple t
In out simplest case no benefits because out repository structure does
not change often. It is just more modern source control thing, but we
can stay on CVS.
Zoran Vasiljevic wrote:
On 20.09.2006, at 21:26, Vlad Seryakov wrote:
Strange, i just ran this command i did not have error messages
On 20.09.2006, at 21:26, Vlad Seryakov wrote:
Strange, i just ran this command i did not have error messages
Yes. I tried it again and it worked here as well.
It seems that this thing is not that stable as
one would think...
I sill miss the real benefit. As we are not hosting
the repository,
Strange, i just ran this command i did not have error messages
user/passwd it will ask on commit
Zoran Vasiljevic wrote:
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
If you have the client installed, simply try for a checkout:
# svn co https://svn.sourceforge.net/svnroot/naviserver/trun
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
If you have the client installed, simply try for a checkout:
# svn co https://svn.sourceforge.net/svnroot/naviserver/trunk/
naviserver
Simple? Simple???
After some struggle, I got that svn client installaed.
And:
zvpb:~/sf/svn zoran$ svn
On 20.09.2006, at 18:32, Vlad Seryakov wrote:
Oh, no hurry, no switching, current SVN copy is just to get to know it
and play with it to see if it is worth switching
For me it looks like weekned job, where I'd rather do
something else. I thougt it to be a download, install
and use. It is far
Oh, no hurry, no switching, current SVN copy is just to get to know it
and play with it to see if it is worth switching
Zoran Vasiljevic wrote:
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
If you have the client installed, simply try for a checkout:
AH, this is really NOT simple...
I
On 20.09.2006, at 18:29, Zoran Vasiljevic wrote:
AH, this is really NOT simple...
For the record:
Reading Package Lists...
Building Dependency Tree...
You might want to run `apt-get -f install' to correct these:
Sorry, but the following packages have unmet dependencies:
storable-pm: Depe
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
If you have the client installed, simply try for a checkout:
AH, this is really NOT simple...
I would say, please _do_not_ switch to svn anything until
I managed to get all this (clients) installed.
When I pull svn-client using Fink command
svn should support http or https, i have just one binary
Zoran Vasiljevic wrote:
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
It is already available, i imported all branches and tags into
SVN, go
to SF and try browse Subversion. Once everybody agree, i will re-
import
most recent CVS
On 20.09.2006, at 17:53, Bernd Eidenschink wrote:
It is already available, i imported all branches and tags into
SVN, go
to SF and try browse Subversion. Once everybody agree, i will re-
import
most recent CVS version.
If you have the client installed, simply try for a checkout:
Nothing
> It is already available, i imported all branches and tags into SVN, go
> to SF and try browse Subversion. Once everybody agree, i will re-import
> most recent CVS version.
If you have the client installed, simply try for a checkout:
# svn co https://svn.sourceforge.net/svnroot/naviserver/trunk/
We need trunk/ only, i guess thos eold tags and branches are CVs
artifacts:-))0
Zoran Vasiljevic wrote:
On 20.09.2006, at 17:30, Vlad Seryakov wrote:
It is already available, i imported all branches and tags into SVN, go
to SF and try browse Subversion. Once everybody agree, i will re-
impor
On 20.09.2006, at 17:30, Vlad Seryakov wrote:
It is already available, i imported all branches and tags into SVN, go
to SF and try browse Subversion. Once everybody agree, i will re-
import
most recent CVS version.
Hm
Rev.Age Author Last log entry
It is already available, i imported all branches and tags into SVN, go
to SF and try browse Subversion. Once everybody agree, i will re-import
most recent CVS version.
Zoran Vasiljevic wrote:
On 20.09.2006, at 17:17, Vlad Seryakov wrote:
Yes, subversion is open-source and available for all
On 20.09.2006, at 17:17, Vlad Seryakov wrote:
Yes, subversion is open-source and available for all platforms.
http://subversion.tigris.org/
OK. So what about the log history from CVS?
I guess there is some kind of magic export/import
that would move all to subversion?
The SF also supports su
Yes, subversion is open-source and available for all platforms.
http://subversion.tigris.org/
Zoran Vasiljevic wrote:
On 20.09.2006, at 16:31, Vlad Seryakov wrote:
Nothing new, old commands are the same:
cvs commit --- svn commit
cvs update --- svn update
New things like:
svn mv
svn rm
...
On 20.09.2006, at 16:31, Vlad Seryakov wrote:
Nothing new, old commands are the same:
cvs commit --- svn commit
cvs update --- svn update
New things like:
svn mv
svn rm
I guess I would need to install new software.
Is there some ugly license attached that will
hunt me later on, as we
Nothing new, old commands are the same:
cvs commit --- svn commit
cvs update --- svn update
New things like:
svn mv
svn rm
Basically, easier file/directory manipulation
also, it caches svn password, so no need to enter it every time:-)))
Zoran Vasiljevic wrote:
On 20.09.2006, at 15:50,
On 20.09.2006, at 15:50, Vlad Seryakov wrote:
What do you think about migrating to SVN?
What (mew) do I have to learn? How is this going
to benefit me or the project?
Not that I'm lazy to learn new things. I just have
very little time, if this is not something that
considerably adds value.
Zoran, Stephen,
What do you think about migrating to SVN?
Vlad Seryakov wrote:
I converted and loaded current CVS HEAD into naviserver SVN repository,
CVS is still primary but we can play with SVN and decide to switch or
keep CVS. Personally, i switched to SVN more than a year ago in all my
p
Hi Vlad,
> Of course i almost all the time work with
> HEAD so i am the simplest case.
At the office we followed the "default" SVN approach with a directory
structure of
# svn list file:///repository/projectname
branches/
tags/
trunk/
It's really nice to simply copy from trunk (or local worki
24 matches
Mail list logo
