From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Re: Checking in files with trailing white space
Date: Sun, 11 Dec 2016 13:31:10 +0000 [thread overview]
Message-ID: <20161211133110.GB14084@acm.fritz.box> (raw)
In-Reply-To: <m360whjnz0.fsf@gnus.org>
Hello, Emacs.
On Sun, Mar 20, 2016 at 02:08:51PM +0100, Lars Magne Ingebrigtsen wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > I'm adding test cases for the shr HTML rendering, and in some of the
> > tests there should really be trailing white space in the result files.
> > Is there a way to say that the test/data/shr directory should be allowed
> > to have trailing spaces in our git/checkin thing?
> Never mind; found it...
Would some kind soul please tell me the recipe. I've just merged master
into a nine-month old branch, and I get lots of these whitespace errors
when I try to commit the merge.
Thanks!
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-12-11 13:31 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161211133110.GB14084@acm.fritz.box \
--to=acm@muc.de \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.