Yes I agree, propchanges in the log etc. is really annoying but I want
go further: equally annoying is propchanges during merge\commit: I merge
a revision and I get a bunch of unrelated propchanges in (to me)
unrelated files and folders (typically propchange on some subfolders,
sometimes propchange on the root folder and often propdelete on misc
unrelated files\folders). Some of my colleges consequently revert\don't
commit those changes, they didn't change those files\folders so I fully
understand. But why is this internal information leaking out to the
users? This is purely an internal "thing" and the server should do this
automatically! When I merge some files in a folder I expect that when I
commit that folder, all changes are included, but now I must always
commit the whole tree to include those propchanges spread around
everywhere. Not good. The correct thing to do would be to make this
invisible on the client and have the server do it automatically. And
showing svn:mergeinfo logs should default to off, making this initially
invisible.
Gunnar.
> In using merge tracking with 1.5.x and other branches, I've
> occasionally been
> annoyed by the fact that mergeinfo mods can often overshadow the meat
> of a
> change. I'd like to add a '--no-props' flag to 'log', 'st', and 'diff'
> which
> would simply cause the subcommand to ignore property changes. It
> wouldn't be
> the default, but it would clean up output and make using merge
> tracking a bit
> easier.
>
> I envision '--no-props' to be an all-or-nothing measure, initially,
> but we if
> the demand was there, we could further expand it to '--without-prop
> FOO' which
> would only omit changes to property FOO.
>
> Thoughts?
>
> -Hyrum
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-04 01:42:43 CEST