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

Re: Creating commits with empty changesets

From: Jö Fahlke <jorrit_at_jorrit.de>
Date: Mon, 7 Nov 2011 23:58:14 +0100

Am Mon, 7. Nov 2011, 23:57:59 +0200 schrieb Daniel Shahaf:
> Assuming you have a versioned file called 'iota',
> % cp iota iota2
> % echo >> iota
> % svn ci iota
> (editor pops up)
> (shell out from editor)
> % cp iota2 iota
> % exit
> (back to editor)
> (enter commit message)
> (exit editor)

That appears to have worked. Although svn seem to kind of remember that the
file 'iota' ('COPYING' in my case) appears to have changed (e.g. with "svn log
COPYING"). This is both an advantage and a disadvantage of this technique: a
disadvantage because files that haven't actually changed are listed as
changed, which is creepy. An advantage, because if you take this into account
you can use all the files that were touched in the faulty commit for 'iota',
and the corrected commit message will appear when you run "svn log" for

Thanks a lot,

[1] Unfortunately, I noticed this only after arbitrarily choosing 'COPYING'...

Jorrit (Jö) Fahlke, Interdisciplinary Center for Scientific Computing,
Heidelberg University, Im Neuenheimer Feld 368, D-69120 Heidelberg
Tel: +49 6221 54 8890 Fax: +49 6221 54 8884
In the beginning the Universe was created.  This has made a lot of
people very angry and been widely regarded as a bad move.
-- Douglas Adams

Received on 2011-11-07 23:58:50 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.