Mark Phippard wrote:
> On Mon, Sep 1, 2008 at 12:21 PM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
>> 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
>> 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.
> Set aside merge tracking for a second. Do you think there would be
> any need for this feature? If not, then it seems like the option
> ought to be about specifically excluding the svn:mergeinfo property
> and nothing else. Something like --ignore-mergeinfo or
Seeing as how mergeinfo is built upon the generic property infrastructure, I'd
rather build something which is property-centric, and could apply to other
properties also. I could conceivably see how one might want to filter out other
property-only changes, to properties such as svn:eol-style or svn:ignore. I can
also imagine that other projects may have project-specific properties for which
this could be useful.
> I still worry a bit about including it in svn status. I see the value
> of it, but I worry people will use it too much and then forget to
> commit those mergeinfo changes because they were not seeing it. I
> suppose as long as it is a command line option, and not a setting in
> config, that is not likely to be a problem though.
That's an understandable concern, but I don't think that it's a showstopper for
this enhancement. This my sound calloused, but if folks get into the habit of
using a commandline switch, it sounds like their problem, not ours.
Received on 2008-09-01 18:37:59 CEST