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

Re: Proposal: --no-props switch for 'log', 'st' and 'diff'

From: Branko ─îibej <brane_at_xbc.nu>
Date: Mon, 01 Sep 2008 23:36:23 +0200

Mark Phippard wrote:
> On Mon, Sep 1, 2008 at 12:37 PM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
>> 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
>>>> 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?
>>> 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
>>> --no-mergeinfo.
>> 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 am obviously making the reverse argument here though. In other
> words, I envision people finding this property information useful,
> where as the svn:mergeinfo information is generally not useful to
> them. I think a switch to shut off all property information is too
> coarse. It'd be interesting to know if we have any enhancement filed
> in the tracker to hide this information for other properties.

Indeed. If the default for log and blame is without -g then it stands to
reason that stat and diff should have the same default, doesn't it. Most
users should be aggressively indifferent to svn:mergeinfo changes. The
fact that svn:mergeinfo is built on the generic property infrastructure
doesn't mean that it's a generic property (svn pd svn:mergeinfo should
IMHO require a --force, for example), or that we should show changes
there by default.

-- Brane

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-01 23:36:40 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.