unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: whitespace-only changes
Date: Thu, 20 Aug 2020 16:54:05 +0200	[thread overview]
Message-ID: <878se9mkqa.fsf@randomsample> (raw)
In-Reply-To: <878se9wigu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 20 Aug 2020 15:32:49 +0200")

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> The tool is Git, and it will treat any change as significant.  I'm not
>> aware of a Git option to ignore some changes based on the log
>> messages.
>
> Me neither, but it sure would be nice to be able to tell git "this is
> not a functional change" (just think of the yearly copyright notice
> update).
>
> git has no way of verifying that it's a non-functional change, of
> course, so it would just be a hint to the UI.  That could then be used
> by nefarious people to sneak in functional changes but mark them as
> non-functional.
>
> So it's probably not a workable idea.

I agree, but just to have mentioned it, at least 'git blame' does
support ignoring commits. These can be given on the commandline or in a
file (see --ignore-rev and --ignore-revs-file since version v2.23). This
file could of course be generated by looking at commit messages.

-David



  reply	other threads:[~2020-08-20 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  3:06 whitespace-only changes Richard Stallman
2020-08-20  8:04 ` Mattias Engdegård
2020-08-20 13:19 ` Eli Zaretskii
2020-08-20 13:32   ` Lars Ingebrigtsen
2020-08-20 14:54     ` David Engster [this message]
2020-08-21  3:33       ` Richard Stallman
2020-08-21  8:55         ` Sergey Organov
2020-08-23  4:42           ` Richard Stallman
2020-08-20 20:50 ` Daniel Martín
2020-08-20 20:54   ` Lars Ingebrigtsen
2020-08-20 21:07     ` Daniel Martín
2020-08-21 13:13 ` Stefan Monnier
2020-08-22  3:51   ` Richard Stallman

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878se9mkqa.fsf@randomsample \
    --to=deng@randomsample.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.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://git.savannah.gnu.org/cgit/emacs.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).