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

RE: Delete revision of an object has no peg revision?

From: Brummer, Byron <ByronBrummer_at_LiveNation.com>
Date: 2007-01-10 02:14:12 CET

Danny van Heumen [danny.vanheumen@hccnet.nl] wrote:
> Michael Sinz wrote:
> > Brummer, Byron wrote:
> >> If url://some/file.txt was Deleted in rev 1234 it makes no sense
> >> running:
> >> svn log -r 1234 url://some/file.txt
> > Maybe there would need to be a way to address this from the user
> > interface, but then there would still be confusion as to what to do
> > the case of a delete/add in the same revision. So, even trying to
> > the user interface problem is difficult as you would need to know
> > of the two same named objects one is trying to identify.
> Do the same difficulties exist if the program could follow the file
> a revision where it still existed?
> Like this:
> svn log -r 1234 url://some/file.txt_at_1233
> At least now there's a "line" to follow, and this "line" would end at
> 1234.
> Or does it still get confused by the replacement 'file.txt'?

        Does it or should it? I'd argue it should, but
        currently as implemented it does not. And that's the
        problem (or at least one of many around this issue): The
        deletion of an object is not considered part of that
        object's history (the add is, the changes are, the removal
        is not, *le sigh*). This means if you want to pull the
        log for the revision in which the object was removed
        you first need to find the exact revision it took
        place (a pita but doable) and then ask for the log
        of that revision using the URL of the base repo, not
        the object's path.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 10 02:15:09 2007

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.