On Thu, Sep 22, 2011 at 11:00 PM, Andreas Krey a.k...@gmx.de wrote:
and Git is just not as user friendly or as polished.
Don't make me rant. The svn user interface (at least the one that
is ontopic here, namely the 'svn' CLI) is horrible...
I suspect this is vi vs. Emacs all over again.
On Wed, 28 Sep 2011 10:06:31 +, David Brodbeck wrote:
...
I suspect this is vi vs. Emacs all over again. People who have gotten used
to the svn user interface (or CVS, for that matter) will find git clumsy;
people who are used to git will find svn clumsy.
Partly, yes. svn has a tendency
On Sat, Sep 24, 2011 at 2:19 PM, Andreas Krey a.k...@gmx.de wrote:
...
If you want tags to be immutable, you know how to make them that way.
I want them mostly immutable, that is, not accidentally, but with -f
(which is pretty much the way any other VCS is doing it).
As far as I can see
On Fri, 23 Sep 2011 01:18:28 +, David Weintraub wrote:
...
I'm not a big fan of Git. Tracking patches and diffs is not the same
as version control,
The trackdiff part is in *addition* to version control proper.
and Git is just not as user friendly or as polished.
Don't make me rant. The
Guten Tag Andreas Krey,
am Freitag, 23. September 2011 um 08:00 schrieben Sie:
The svn user interface (at least the one that
is ontopic here, namely the 'svn' CLI) is horrible, mostly due to
the fact that svn only pretends to have branches and doesn't have
tags at all. (It replaces them by a
On Fri, Sep 23, 2011 at 12:18 AM, David Weintraub qazw...@gmail.com wrote:
Having a publicly available Subversion repository is the best way. The
problem is what do you do if you don't have that.
VPN's are the usual approach to having access over the internet to
something that isn't public.
On Fri, Sep 23, 2011 at 1:00 AM, Andreas Krey a.k...@gmx.de wrote:
Don't make me rant. The svn user interface (at least the one that
is ontopic here, namely the 'svn' CLI) is horrible, mostly due to
the fact that svn only pretends to have branches and doesn't have
tags at all. (It replaces
One of the nice thing about Dropbox is that you can share files
between various users. I will sometimes keep a Subversion repository
on Dropbox, so I can access it on various systems. Right now, it's
just for me to use.
Here's the scenario:
* I have my Dropbox under $HOME/Dropbox.
* I create a
Sharing the repository and having everyone run their own server
defeats the purpose.Not just with SVN but with any sepup where we
have a server process and a data store the pourpose of the server
mostly is to serialize or control access to the data, maintain locks
and so on.
On Thu, Sep 22,
On Thu, Sep 22, 2011 at 1:40 PM, David Weintraub qazw...@gmail.com wrote:
One of the nice thing about Dropbox is that you can share files
between various users. I will sometimes keep a Subversion repository
on Dropbox, so I can access it on various systems. Right now, it's
just for me to use.
On Thu, Sep 22, 2011 at 20:40, David Weintraub qazw...@gmail.com wrote:
One of the nice thing about Dropbox is that you can share files
between various users. I will sometimes keep a Subversion repository
on Dropbox, so I can access it on various systems. Right now, it's
just for me to use.
Ben Smith-Mannschott wrote on Thu, Sep 22, 2011 at 20:49:35 +0200:
On Thu, Sep 22, 2011 at 20:40, David Weintraub qazw...@gmail.com wrote:
One of the nice thing about Dropbox is that you can share files
between various users. I will sometimes keep a Subversion repository
on Dropbox, so I
My first impression is that of course this will not work. But let's
be more positive. What would work?
1) Use your SVN server to maintain versions and history and then
checkout a working directory to the dropbox. You can even have
multiple working directories in the dropbox.
2. put your SVN
13 matches
Mail list logo
