Markus Schaber wrote on Wed, Jul 27, 2011 at 09:37:38 +0200:
> Hi, Andreas,
>
> Von: Andreas Krey [mailto:a.k...@gmx.de]
>
> > On Tue, 26 Jul 2011 13:55:17 +, Les Mikesell wrote:
> > ...
> > > How could it possibly be up to date if there has been a commit since
> > > the last time it was upd
Hi, Andreas,
Von: Andreas Krey [mailto:a.k...@gmx.de]
> On Tue, 26 Jul 2011 13:55:17 +, Les Mikesell wrote:
> ...
> > How could it possibly be up to date if there has been a commit since
> > the last time it was updated?
>
> Because the commit came from my WC. My WC was up to date before th
On 7/26/11 5:14 PM, Andy Canfield wrote:
I shy away from svnsync right now because it requires me to get TWO of these
Subversion systems running. At present I am almost able to get one running.
Almost.
You don't need a 2nd server. Svnsync is a client to both repos, but the side it
is writin
On 7/26/11 4:23 PM, Andreas Krey wrote:
Because the commit came from my WC. My WC was up to date before the
commit, and the only things that change have been in my WC already,
so there is no possible way my WC can not be up to date. Except that it
'forgets' to update the WC revision info, and r
On 07/27/2011 01:34 AM, Nico Kadel-Garcia wrote:
On Tue, Jul 26, 2011 at 2:33 AM, Andy Canfield wrote:
For your information, this is my backup script. It produces a zip file that
can be tranported to another computer. The zip file unpacks into a
repository collection, giving, for each
On Tue, 26 Jul 2011 15:59:59 +, Les Mikesell wrote:
...
> >Because the commit came from my WC. My WC was up to date before the
> >commit, and the only things that change have been in my WC already,
> >so there is no possible way my WC can not be up to date. Except that it
> >'forgets' to update
On 7/26/2011 3:03 PM, Andreas Krey wrote:
On Tue, 26 Jul 2011 13:55:17 +, Les Mikesell wrote:
...
How could it possibly be up to date if there has been a commit since the
last time it was updated?
Because the commit came from my WC. My WC was up to date before the
commit, and the only thin
On Tue, 26 Jul 2011 13:55:17 +, Les Mikesell wrote:
...
> How could it possibly be up to date if there has been a commit since the
> last time it was updated?
Because the commit came from my WC. My WC was up to date before the
commit, and the only things that change have been in my WC already
On 7/26/2011 1:47 PM, Andreas Krey wrote:
This is one of the high strangitude svn behaviour artefacts: That you
can't do two consecutive commits without getting an error (in some
relatively popular cases).
And you generally shouldn't be doing that unless there is some special
need to avoid pi
On Tue, 26 Jul 2011 11:53:15 +, Les Mikesell wrote:
> On 7/26/2011 11:42 AM, Andreas Krey wrote:
...
> >This is one of the high strangitude svn behaviour artefacts: That you
> >can't do two consecutive commits without getting an error (in some
> >relatively popular cases).
>
> And you generall
On Tue, Jul 26, 2011 at 06:42:39PM +0200, Andreas Krey wrote:
> On Tue, 26 Jul 2011 10:09:47 +, Les Mikesell wrote:
> ...
> > Yes, but it is then a mixed rev and needs an update. That is, the
> > changes you committed belong to the rev the commit creates while the
> > unchanged files belong
On 7/26/2011 11:42 AM, Andreas Krey wrote:
On Tue, 26 Jul 2011 10:09:47 +, Les Mikesell wrote:
...
Yes, but it is then a mixed rev and needs an update. That is, the
changes you committed belong to the rev the commit creates while the
unchanged files belong to the rev of the prior update or
On Tue, 26 Jul 2011 10:09:47 +, Les Mikesell wrote:
...
> Yes, but it is then a mixed rev and needs an update. That is, the
> changes you committed belong to the rev the commit creates while the
> unchanged files belong to the rev of the prior update or checkout.
This is one of the high str
On Tue, 26 Jul 2011 16:11:27 +, Markus Schaber wrote:
...
> > Von: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
...
> > disk, and thus not to be trusted too much. For safety an external hard
> > disk, flushed, should be good enough. No need for an entire other host.
> > Yes?
>
> Only if the
On 7/26/2011 7:48 AM, Andy Canfield wrote:
As I understand Subversion,
[a] The server has no idea who has a working copy.
[b] The checkout builds a working copy on the workstation from the
server's repository.
[c] What is on the developers hard disk is a working copy.
[d] What is on the develope
Hi,
> Von: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
> > And make /backup a separate filesystem, preferably on a different host
> > or some disk storage that runs independently from the host.
> In Linux a separate "filesystem" is often another partition on the hard
> disk, and thus not to be
On 07/26/2011 04:20 PM, Stefan Sperling wrote:
On Tue, Jul 26, 2011 at 01:33:09PM +0700, Andy Canfield wrote:
For your information, this is my backup script. It produces a zip
file that can be tranported to another computer. The zip file
unpacks into a repository collection, giving, for each
On Tue, Jul 26, 2011 at 01:33:09PM +0700, Andy Canfield wrote:
> For your information, this is my backup script. It produces a zip
> file that can be tranported to another computer. The zip file
> unpacks into a repository collection, giving, for each repository, a
> hotcopy of the re
On 7/25/2011 11:33 PM, Andy Canfield wrote:
For your information, this is my backup script. It produces a zip file
that can be tranported to another computer. The zip file unpacks into
a repository collection, giving, for each repository, a hotcopy of the
repository and a dump of the
For your information, this is my backup script. It produces a zip file
that can be tranported to another computer. The zip file unpacks into a
repository collection, giving, for each repository, a hotcopy of the
repository and a dump of the repository. The hotcopy can be reloaded on
a computer
20 matches
Mail list logo
