From: Pete Harlan <pgit@pcharlan•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: Neal Kreitzinger <nkreitzinger@gmail•com>,
Neal Kreitzinger <neal@rsss•com>,
git@vger•kernel.org
Subject: Re: filtering out mode-change-only changes
Date: Sat, 03 Mar 2012 14:16:43 -0800 [thread overview]
Message-ID: <4F52984B.5050805@pcharlan.com> (raw)
In-Reply-To: <7vsjhts9hu.fsf@alter.siamese.dyndns.org>
On 2/29/2012 11:52 AM, Junio C Hamano wrote:
> Neal Kreitzinger<nkreitzinger@gmail•com> writes:
>
>> A3-2: (Some Desired Options)
>> --name-status learns a new status for file-mode-only changes (ie, "P"
>> for "P"ermissions).
>
> After reading everything above I omitted from your response in my quote, I
> still do not get the feeling that these willy-nilly mode changes that you
> are suffering from is a problem that is general enough to warrant such a
> change, even if such a change is done as an optional feature.
I'll add a vote for the usefulness of the option.
I'm dealing with a repo whose history occasionally has commits that do a
handful of real changes mixed in with tens of thousands of mistaken mode
changes. (New workflow is fixed but it is infeasible to fix history at
this point.) It's cumbersome filtering away the noise.
If Git's diff engine could ignore mode changes that would be a big help.
Regards,
--
Pete Harlan
pgit@pcharlan•com
next prev parent reply other threads:[~2012-03-03 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:31 filtering out mode-change-only changes Neal Kreitzinger
2012-02-29 3:40 ` Junio C Hamano
2012-02-29 3:52 ` Junio C Hamano
2012-02-29 19:11 ` Neal Kreitzinger
2012-02-29 19:52 ` Junio C Hamano
2012-03-03 22:16 ` Pete Harlan [this message]
2012-02-29 22:17 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F52984B.5050805@pcharlan.com \
--to=pgit@pcharlan$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=neal@rsss$(echo .)com \
--cc=nkreitzinger@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox