[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Is a two step commit possible?

From: Kraja, Toni <Toni.Kraja_at_bci.tu-dortmund.de>
Date: Fri, 31 Oct 2008 13:01:38 +0100


I am using one computer that is used for developing a web project, then
a server where the web project is running at and a third server that
provides the svn repository folder.

Now it works this way:
First i commit to the second server and then let the first sever update
his own files.

I would like to use svn now this way:

First: if i have worked on a file, commit it to the first server to test
if the project with the current changes is working as excepted.

Second: Commit the changes then to the second server to have a stable
copy on there.

Is there any easy way to change it this way? I except that i have to
announce somehow the first server folder as the repository and then let
the second server do updates if necessary, am i right?

What disturbs me on this idea is, that a problem i have with the way it
works now would still occur: Unnecessary high counting of the revision
number and filling the svn history with too many minor changes that had
to be made for testing.

Best regards

Toni Kraja

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-31 23:24:39 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.