From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Checking in files with trailing white space
Date: Tue, 13 Dec 2016 10:39:12 -0800 [thread overview]
Message-ID: <3c9e726c-215d-a4e9-a353-1475f2ddc504@cs.ucla.edu> (raw)
In-Reply-To: <20161213182822.GA2705@acm.fritz.box>
On 12/13/2016 10:28 AM, Alan Mackenzie wrote:
> Alternatively, could the pre-commit git hook be adapted to warn the
> committer about trailing space and ask him for confirmation? I couldn't
> see an easy way over the weekend, but it might be possible, somehow.
I don't see an easy way either. Part of the problem is that some
developers commit with vc and some do not. If you use vc, perhaps you
could cook up something that works with vc; as I don't use vc to commit,
I'm not the best person to give advice in that area. Plus, I'd rather
not have to deal with source files containing trailing white space (it
is *such* a pain in so many ways), so my motivation to help in this area
is somewhat limited....
next prev parent reply other threads:[~2016-12-13 18:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 12:55 Checking in files with trailing white space Lars Magne Ingebrigtsen
2016-03-20 13:08 ` Lars Magne Ingebrigtsen
2016-12-11 13:31 ` Alan Mackenzie
2016-12-11 18:50 ` Lars Ingebrigtsen
2016-12-12 22:16 ` Alan Mackenzie
2016-12-12 22:57 ` Paul Eggert
2016-12-13 3:32 ` Eli Zaretskii
2016-12-13 7:31 ` Paul Eggert
2016-12-13 16:01 ` Eli Zaretskii
2016-12-13 18:33 ` Paul Eggert
2016-12-13 19:00 ` Eli Zaretskii
2016-12-13 22:39 ` Paul Eggert
2016-12-14 3:31 ` Eli Zaretskii
2016-12-14 7:47 ` Paul Eggert
2016-12-14 15:32 ` Eli Zaretskii
2016-12-14 18:15 ` Paul Eggert
2016-12-14 19:26 ` Eli Zaretskii
2016-12-13 18:28 ` Alan Mackenzie
2016-12-13 18:39 ` Paul Eggert [this message]
2016-03-21 13:10 ` Stefan Monnier
2016-03-21 13:59 ` Lars Magne Ingebrigtsen
2016-03-21 18:09 ` Paul Eggert
2016-04-04 20:05 ` Lars Magne Ingebrigtsen
2016-04-04 21:55 ` Paul Eggert
2016-04-24 13:13 ` Lars Magne Ingebrigtsen
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=3c9e726c-215d-a4e9-a353-1475f2ddc504@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).