From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: vc-region-history promotion (was: removing white space highlight) Date: Thu, 25 Feb 2016 15:10:44 -0500 Message-ID: References: <87ziupsl8z.fsf@debian.uxu> <87povkv9xl.fsf@robertthorpeconsulting.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1456431081 13868 80.91.229.3 (25 Feb 2016 20:11:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Feb 2016 20:11:21 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Feb 25 21:11:09 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aZ2Ff-0000OA-GJ for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Feb 2016 21:11:07 +0100 Original-Received: from localhost ([::1]:45601 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZ2Fe-0007Ti-PF for geh-help-gnu-emacs@m.gmane.org; Thu, 25 Feb 2016 15:11:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZ2FS-0007TK-Kr for help-gnu-emacs@gnu.org; Thu, 25 Feb 2016 15:10:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZ2FP-0002ff-TF for help-gnu-emacs@gnu.org; Thu, 25 Feb 2016 15:10:54 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:52793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZ2FP-0002fI-Ji for help-gnu-emacs@gnu.org; Thu, 25 Feb 2016 15:10:51 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aZ2FO-0000Bu-1O for help-gnu-emacs@gnu.org; Thu, 25 Feb 2016 21:10:50 +0100 Original-Received: from 76-10-161-227.dsl.teksavvy.com ([76.10.161.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 Feb 2016 21:10:50 +0100 Original-Received: from monnier by 76-10-161-227.dsl.teksavvy.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 Feb 2016 21:10:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 25 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 76-10-161-227.dsl.teksavvy.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:PvHgRTClZ+Kt8+TrV2zwY5EtjE0= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:109313 Archived-At: > The question is what about the *VC annotated* file? If I blame a > particular section of a file how do I know who wrote that code and when? > The problem is I can't tell because any particular check-in could be a > whitespace change. I'd actually have to start digging through older > versions. I agree such "unrelated changes" are generally undesired. [ In the case of Emacs's own source code, we try to follow a policy where people are allowed to "fix whitespace" but only in those places where they're making other changes as well. So a whose-file cleanup of trailing whitespace is not accepted. ] This said, I recently stopped using vc-annotate and so don't care nearly as much any more: instead I use vc-region-history, which gives me much more detailed information where such whitespace games aren't very much of a problem. I'd been dreaming of a functionality like vc-region-history ever since I started using TLA (i.e. before Bazaar existed), and oddly enough so far only Git offers that feature, AFAIK. vc-region-history also solves the problem of vc-annotate's blindness to code removal (the vc-annotate output won't tell you where code was removed, and even less by whom). Stefan