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

Re: SVN Import command

From: <kmradke_at_rockwellcollins.com>
Date: Fri, 3 May 2013 12:43:39 -0500

> I don't understand why I can't simply over-write the existing file in
the
> directory? On many occasions, a build may only result in one new
executable.
> To have to delete/rename the entire directory seems like overkill.

While it kinda defeats the purpose of Subversion, you can use the svnmucc
utility to "overwrite" an existing file, even with the same contents:

svnmucc put test.txt http://server/kmr_test/trunk/foo/test.txt -m"Add
file"
r479 committed by kmradke at 2013-05-03T17:36:00.823078Z

svnmucc put test.txt http://server/kmr_test/trunk/foo/test.txt
-m"Overwrite file"

svn log http://server/kmr_test/trunk/foo/test.txt
------------------------------------------------------------------------
r480 | kmradke | 2013-05-03 12:36:12 -0500 (Fri, 03 May 2013) | 1 line

Overwrite file
------------------------------------------------------------------------
r479 | kmradke | 2013-05-03 12:36:00 -0500 (Fri, 03 May 2013) | 1 line

Add file
------------------------------------------------------------------------

svn diff -r479:480 http://server/kmr_test/trunk/foo/test.txt

In this case no local working copy is needed, but it will happily
let you overwrite the file with the same contents and create create
a new subversion revision. Note that the complete file contents
will be sent to the server each time.

If you are on Windows I'm not sure what distributions include svnmucc.
(TortoiseSVN does not)

Kevin R.
Received on 2013-05-03 19:44:15 CEST

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.