On Sat, 12 Jun 2004 00:45:31 +0900, Pier Fumagalli [EMAIL PROTECTED] wrote:
That is when I started feeling that having all my history in big
berkeley DB files which I could not cat was kinda scary...
That's why the Subversion developers kindly gave us all sorts of ways
to make backups:
On Jun 14, 2004, at 8:37 AM, Ask Bjørn Hansen wrote:
On Sat, 12 Jun 2004 00:45:31 +0900, Pier Fumagalli
[EMAIL PROTECTED] wrote:
That is when I started feeling that having all my history in big
berkeley DB files which I could not cat was kinda scary...
That's why the Subversion developers kindly
Dirk-Willem van Gulik wrote:
On Jun 11, 2004, at 2:20 PM, Henri Yandell wrote:
1) Website needs to be in SVN, else we'll still need accounts for
everyone
who wants to modify their site annd do releases. Are the SVN based
projects taking an approach that handles this? Will it?
In the company we
Dirk-Willem van Gulik wrote:
On Jun 11, 2004, at 10:35 PM, Stefano Mazzocchi wrote:
Brian McCallister wrote:
[EMAIL PROTECTED] mccallister]$ umask
umask 0002
[EMAIL PROTECTED] mccallister]$ umask -S
u=rwx,g=rwx,o=rx
and set the group sticky bit on the repository home so that group is
preserved
On Jun 14, 2004, at 6:02 PM, Stefano Mazzocchi wrote:
Dirk-Willem van Gulik wrote:
On Jun 11, 2004, at 2:20 PM, Henri Yandell wrote:
1) Website needs to be in SVN, else we'll still need accounts for
everyone
who wants to modify their site annd do releases. Are the SVN based
projects taking an
On Jun 14, 2004, at 6:04 PM, Stefano Mazzocchi wrote:
Dirk-Willem van Gulik wrote:
On Jun 11, 2004, at 10:35 PM, Stefano Mazzocchi wrote:
Brian McCallister wrote:
.. snipped subtle umask magic which needs to fit the
... operational culture of the community.
..
good hint, thanks.
As we had some
On Mon, Jun 14, 2004 at 06:13:17PM +0200, Dirk-Willem van Gulik wrote:
...
Cause it actually lives on another machine than the repo (with
an ocean in between). We tried this however for the toy site
wleiden.webweaving.org:8080/svn/node-config/ (just 3.5Gb and
a few thousands commits sofar) and
I second what Niclas said. It's a rare situation, but when it happens,
it's a pain to recover (like, you press ^C because you regretted a
commit but you end up regretting have pressed ^C due to the mess it
caused :-)
Felipe
On Fri, 2004-06-11 at 12:11, Niclas Hedhman wrote:
On Friday 11 June
On Jun 11, 2004, at 10:35 PM, Stefano Mazzocchi wrote:
Brian McCallister wrote:
[EMAIL PROTECTED] mccallister]$ umask
umask 0002
[EMAIL PROTECTED] mccallister]$ umask -S
u=rwx,g=rwx,o=rx
and set the group sticky bit on the repository home so that group is
preserved
good hint, thanks.
As we had
On Jun 11, 2004, at 5:33 PM, Brian W. Fitzpatrick wrote:
On Fri, 2004-06-11 at 10:23, Niclas Hedhman wrote:
On Friday 11 June 2004 18:17, Dirk-Willem van Gulik wrote:
On a positive note; do look at subversion; play with it - and note
that
its modern infrastructure and standard based protocols do
On Fri, 2004-06-11 at 17:43, James Duncan Davidson wrote:
On Jun 11, 2004, at 08:45, Pier Fumagalli wrote:
That is when I started feeling that having all my history in big
berkeley DB files which I could not cat was kinda scary...
Yeah, it's a bit scary for the largish project that I'm
Heu.., a couple of questions from the totally ignorant (me).
1) what is an atomic commit? Do I need to wear a irradiation-protective
suit to use it?
2) How easy is it to migrate an existing CVS repo to subversion?
Thanks in advance for your response, even if it is RTFM.
At 01:04 PM 6/11/2004
dummy -dP flags to update so that
I can stop getting errors...
Did I mention atomic commits ?
-Brian
ps: atomic commits
On Jun 11, 2004, at 6:17 AM, Dirk-Willem van Gulik wrote:
In reaction to some worried emails related to some projects moving
from CVS to Subversion.
- Do
, but apparently other
people encountered them.
2) How easy is it to migrate an existing CVS repo to subversion?
infra has nifty scripts to convert everything including branches and
history.
Vadim
Thanks in advance for your response, even if it is RTFM.
At 01:04 PM 6/11/2004, Brian McCallister wrote:
I
On Fri, 2004-06-11 at 07:20, Henri Yandell wrote:
2) Tagging is clumsy. (I may just not be seeing it in the manual). It
seems hard to tag a directory and files not in that directory with a tag,
or tag a directory without tagging every file in it.
Since a tag is essentially a 'copy' in
administration, that's when the
transactions really rock.
-Jim Moore
- Original Message -
From: Vadim Gritsenko [EMAIL PROTECTED]
To: community@apache.org
Sent: Friday, June 11, 2004 8:21 AM
Subject: Re: CVS and Subversion
Ceki Gülcü wrote:
Heu.., a couple of questions from
On Fri, 2004-06-11 at 08:29, Henri Yandell wrote:
On Fri, 11 Jun 2004, Brian W. Fitzpatrick wrote:
I know of no uses cases for what you're describing... do you have one?
Two of them.
1) Common for a piece of taggable code to inherit something outside of its
directory, usually either a
On Friday 11 June 2004 21:02, Jim Moore wrote:
Actually, the all or nothing part of the transaction isn't a big deal
because, as you said, it's very rare that a commit in CVS would fail.
But I often change my mind half way through... (lazy thought-loading), Ctrl-C,
and CVS is 'half way
On Friday 11 June 2004 18:17, Dirk-Willem van Gulik wrote:
On a positive note; do look at subversion; play with it - and note that
its modern infrastructure and standard based protocols do allow for
levels of integration previously hard to attain.
Another note that noone seems to consider,
On Jun 11, 2004, at 5:23 PM, Niclas Hedhman wrote:
Subversion eats almost all CPU cycles on a 2.4 Linux Kernel, on
updates and
commits. Often so much that even the mouse is no longer tracking, and
always
making my entire desktop fairly unresponsive. And for Avalon that means
~1minute on my
On Fri, 2004-06-11 at 10:23, Niclas Hedhman wrote:
On Friday 11 June 2004 18:17, Dirk-Willem van Gulik wrote:
On a positive note; do look at subversion; play with it - and note that
its modern infrastructure and standard based protocols do allow for
levels of integration previously hard
* Niclas Hedhman ([EMAIL PROTECTED]) wrote :
Another note that noone seems to consider, which I think is fairly important
(read annoying);
Subversion eats almost all CPU cycles on a 2.4 Linux Kernel, on updates and
commits. Often so much that even the mouse is no longer tracking, and
On Friday 11 June 2004 23:23, Niclas Hedhman wrote:
Subversion eats almost all CPU cycles on a 2.4 Linux Kernel, on updates and
commits.
Am I the only one who have this problem???
I am only using SVN CLI.
[EMAIL PROTECTED] niclas]$ uname -a
Linux f2.hedhman.org 2.4.20-20.9 #1 Mon Aug 18
Pier Fumagalli wrote:
On 11 Jun 2004, at 22:02, Jim Moore wrote:
Actually, the all or nothing part of the transaction isn't a big deal
because, as you said, it's very rare that a commit in CVS would fail.
Problem being (though) is that I've seen Subversion (1.0.2 under Linux)
fail right because
We hit this a number of times with svn+ssh until we got everyone to
properly set their umask. haven't had it happen since then, however.
-Brian
On Jun 11, 2004, at 2:15 PM, Stefano Mazzocchi wrote:
Pier Fumagalli wrote:
On 11 Jun 2004, at 22:02, Jim Moore wrote:
Actually, the all or nothing part
Brian W. Fitzpatrick wrote:
On Fri, 2004-06-11 at 13:15, Stefano Mazzocchi wrote:
Pier Fumagalli wrote:
On 11 Jun 2004, at 22:02, Jim Moore wrote:
Actually, the all or nothing part of the transaction isn't a big deal
because, as you said, it's very rare that a commit in CVS would fail.
Problem
[EMAIL PROTECTED] mccallister]$ umask
umask 0002
[EMAIL PROTECTED] mccallister]$ umask -S
u=rwx,g=rwx,o=rx
and set the group sticky bit on the repository home so that group is
preserved
-Brian
On Jun 11, 2004, at 3:00 PM, Stefano Mazzocchi wrote:
Brian McCallister wrote:
We hit this a number of
27 matches
Mail list logo
