From mboxrd@z Thu Jan 1 00:00:00 1970 From: cnighswonger Subject: Re: [PATCH] blame: can specify shas of commits to ignore on command line Date: Thu, 8 Mar 2012 13:01:13 -0800 (PST) Message-ID: <1331240473379-7356224.post@n2.nabble.com> References: <1272939687-17686-1-git-send-email-dgreid@gmail.com> <4BE0918C.9090204@lsrfire.ath.cx> <7vtyqnl19w.fsf@alter.siamese.dyndns.org> <7vfx27kjr6.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Thu Mar 08 22:01:23 2012 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1S5kSd-0006qu-1g for gcvg-git-2@plane.gmane.org; Thu, 08 Mar 2012 22:01:19 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751896Ab2CHVBO (ORCPT ); Thu, 8 Mar 2012 16:01:14 -0500 Received: from sam.nabble.com ([216.139.236.26]:60668 "EHLO sam.nabble.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751300Ab2CHVBO (ORCPT ); Thu, 8 Mar 2012 16:01:14 -0500 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S5kSX-00042F-CX for git@vger.kernel.org; Thu, 08 Mar 2012 13:01:13 -0800 In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: 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.