From: cnighswonger <chris.nighswonger@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] blame: can specify shas of commits to ignore on command line
Date: Thu, 8 Mar 2012 13:01:13 -0800 (PST) [thread overview]
Message-ID: <1331240473379-7356224.post@n2.nabble.com> (raw)
In-Reply-To: <l2wfd211a421005042228rd6386ff9k9bc54c5862209785@mail.gmail.com>
I'm not subscribed to the list, so please reply-to-all or cc me on responses.
Is this feature dead? There seems to be some question about the value of
such a feature in the discussion along this thread, however, such a feature
would have the wonderful benefit of allowing a change such as that being
discussed here:
http://koha.1045719.n5.nabble.com/Koha-3-8-release-schedule-amp-perltidy-process-td5547369.html
to be made and yet preserve the usefulness of git-blame.
To recap the issue in the thread at koha-devel:
A massive perl-tidy is being considered to be applied project wide in a
single commit. The real show-stopper is that this breaks git-blame. If
git-blame could be told to ignore that single commit id, life would be good
(I think).
At any rate it provides a use-case which might justify such a feature.
Kind Regards,
Chris
--
View this message in context: http://git.661346.n2.nabble.com/PATCH-blame-can-specify-shas-of-commits-to-ignore-on-command-line-tp5001395p7356224.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-03-08 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 2:21 [PATCH] blame: can specify shas of commits to ignore on command line Dylan Reid
2010-05-04 21:28 ` René Scharfe
2010-05-04 21:46 ` Dylan Reid
2010-05-04 23:01 ` Junio C Hamano
2010-05-04 23:08 ` Dylan Reid
2010-05-05 5:19 ` Junio C Hamano
2010-05-05 5:28 ` Dylan Reid
2012-03-08 21:01 ` cnighswonger [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1331240473379-7356224.post@n2.nabble.com \
--to=chris.nighswonger@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).