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

Re: Commit dialog suggestion

From: Brian Gideon <briangideon_at_yahoo.com>
Date: Mon, 29 Sep 2008 06:13:58 -0700 (PDT)

On Sep 28, 3:20 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Brian Gideon wrote:
> > Whenever you do a copy/move/rename operation Subversion puts an empty
> > svn:mergeinfo value on the effected nodes.  I'm really struggling with
> > this because it causes all sorts of chaos in the log.  Not only does
> > it pollute the log with files whose contents haven't changed it also
> > causes strange and unrelated revisions to appear when including merged
> > revisions.  One work around that has been published is to delete these
> > empty svn:mergeinfo properties before they get committed.  That's what
> > I have been doing.
>
> > This leads me to my suggestion for TortoiseSVN.  One thing I noticed
> > about the commit dialog is that it will display files that have their
> > properties modified.  That's fine and dandy.  But, it fails to do so
> > on files that have been copied, moved, or renamed.  Anytime a file has
> > the text status "added (+)" the property status is always blank even
> > if a property really was added.  Obviously, that makes it difficult to
> > spot the situation I describe above.  It would be nice if the property
> > status column worked when doing a copy/move/rename operation as well.
>
> Such a change would have to be done in the svn core library, not TSVN
> itself. It's the library API that does not return property info for
> added items.
>
> Stefan

Ah...yes. I that makes sense.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-29 15:14:30 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.