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

Re: Revisions with no changes [Was: AW: Merge commit message generation bogus]

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 23 May 2014 19:28:31 +0200

On 23.05.2014 19:19, Ben Fritz wrote:
> On Fri, May 23, 2014 at 12:11 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> One edge case: there are revisions that don't touch any paths like this one:
>> https://code.google.com/p/tortoisesvn/source/detail?r=4868
>> but I guess that's one situation where it's ok to not use the message
>> (this rev doesn't have a commit message, but it could have).
> You piqued my curiosity.
> What does that revision actually change? I can't even figure out how
> it may have been created!

The revision before that one is the same :)

IIRC, this was a faulty commit done by the tigris admins (back when the
repo was hosted on tigris.org), but then removed later because it
contained non-public data.
You can remove revisions or data from revisions using svndumpfilter if
you have to.
Of course, in this case the whole commit was removed. You can however
only remove the committed files but leave the message and all other
metadata intact, and I know of some users who have revisions like that
in their repositories.

And those two revisions caused a lot of problems already, because that's
really a special situation which we don't always check for in the TSVN
code ;)
I remember a lot of problems because of revisions like these, especially
in the revision graph.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-05-23 19:28:32 CEST

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

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