On Wed, May 18, 2011 at 9:32 AM, Bert Huijben <b...@qqmail.nl> wrote: > It would completely break mergetracking for about a dozen reasons :( > > I'll answer more detailed later, but this would just remove the > property everywhere. > > And if you could hide it in a better way while still storing it in the > wc, you would always forget to commit your mergeinfo only changes. > > Bert Huijben (Cell phone) From: Daniel Shahaf > Sent: woensdag 18 mei 2011 8:55 > To: dev@subversion.apache.org > Subject: [random line of thought] Hiding svn:mergeinfo > Mike remarked that svn:mergeinfo should never have been user-visible... > > So: what if we made svn_property_kind(NULL, SVN_PROP_MERGEINFO) return > a value other than svn_prop_regular_kind, at least when both server and > client were ≥1.7? Would that have any useful side-effects? > > > [I suspect it might, but want to hear others' thoughts before laying > out my own.]
I don't think hiding it completely is the way to go, but there has been some half-implemented code to filter propchanges from various operations. Completing this, and enabling it by default on selected commands may scratch the same itch. -Hyrum
