From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Checking in files with trailing white space
Date: Tue, 13 Dec 2016 05:32:17 +0200 [thread overview]
Message-ID: <83wpf4bj26.fsf@gnu.org> (raw)
In-Reply-To: <cd2ee9b5-e174-21b3-ba03-9585924143b8@cs.ucla.edu> (message from Paul Eggert on Mon, 12 Dec 2016 14:57:42 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 12 Dec 2016 14:57:42 -0800
> Cc: emacs-devel@gnu.org
>
> Similarly, I'd rather avoid committing binary data. It's easier to read
> and review text files, given the tools we have. Any tests that require
> binary data can generate the data when the test is run.
How would you generate the likes of test/manual/etags/ETAGS.good_1?
next prev parent reply other threads:[~2016-12-13 3:32 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 [this message]
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=83wpf4bj26.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=eggert@cs.ucla.edu \
--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 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.