From: Junio C Hamano <gitster@pobox.com>
To: Anders Melchiorsen <anders@kalibalik.dk>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: --diff-filter=T does not list x changes
Date: Fri, 17 Oct 2008 16:58:30 -0700 [thread overview]
Message-ID: <7vzll2epuh.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 87wsg7m2xp.fsf@kalibalik.dk
Anders Melchiorsen <anders@kalibalik.dk> writes:
> ... way to pick out the commits that toggle the x
> bit? That is a problem that I am facing, with no solution shown so far ...
Are you interested in executable-bit only change, or any change that
contains changes to the executable-bit? If I were looking for the latter,
probably finding "^:100664 100775 " (or the other way around) in log --raw
(or whatchanged) output would be what I would do --- the mode changes are
rare enough in a sane project, so I wouldn't mind having to do such
scripting as needed.
There are other "commit pickers" such as -S<strting> and --diff-filter
that do not absolutely have to exist (iow, they could also be scripted),
but what they pick earned easy shortcuts because the need is very common.
Once you can demonstrate that the need to pick executable-bit changes is
also very common, _and_ if you can come up with a clean solution, we might
add a commit picker that looks for changes in executable-ness in the
future. I dunno.
next prev parent reply other threads:[~2008-10-17 23:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 18:42 --diff-filter=T does not list x changes Anders Melchiorsen
2008-10-16 10:22 ` Jeff King
2008-10-17 2:00 ` Junio C Hamano
2008-10-17 7:08 ` Anders Melchiorsen
2008-10-17 8:29 ` Junio C Hamano
2008-10-17 19:33 ` Anders Melchiorsen
2008-10-17 23:58 ` Junio C Hamano [this message]
2008-10-18 8:49 ` [PATCH] Documentation: diff-filter=T only tests for symlink changes Anders Melchiorsen
2008-10-18 13:40 ` Nanako Shiraishi
2008-10-18 18:37 ` Junio C Hamano
2008-10-18 18:08 ` Junio C Hamano
2008-10-19 1:04 ` Nanako Shiraishi
2008-10-19 10:29 ` Anders Melchiorsen
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=7vzll2epuh.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=anders@kalibalik.dk \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).