From: Paul Eggert <eggert@cs.ucla.edu>
To: 20290@debbugs.gnu.org
Subject: bug#20290: 25.0.50; Use unified diff format by default, and recommend using it in reports and patches
Date: Sun, 12 Apr 2015 16:30:01 -0700 [thread overview]
Message-ID: <552AFFF9.90501@cs.ucla.edu> (raw)
In-Reply-To: <86bnix6p9l.fsf@yandex.ru>
As I recall, RMS preferred diff -c to diff -u, and that is partly why
trouble.texi suggests -c over -u and why diff-switches defaults to -c. Also,
traditional Unix 'diff' lacked -u; although GNU diff had -u starting in 1990,
diff -u wasn't standardized by POSIX until 2008.
These days -u format is far more popular than -c format in practice, and I
expect that most active Emacs developers prefer -u, so it's appropriate for
Emacs to default to -u and for trouble.texi to suggest it.
I suppose that in theory there is the issue of Emacs running on an older
POSIXish platform where 'diff' does not support -u. I don't have access to any
such platform, though. I can confirm that Solaris 10 diff (2005) supports '-u'.
So perhaps we don't need to worry about this.
next prev parent reply other threads:[~2015-04-12 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 20:05 bug#20290: 25.0.50; Use unified diff format by default, and recommend using it in reports and patches Dmitry Gutov
2015-04-10 7:26 ` Eli Zaretskii
2015-04-10 11:59 ` Dmitry Gutov
2015-04-10 7:33 ` Glenn Morris
2015-04-10 12:26 ` Dmitry Gutov
2015-04-10 15:55 ` Andreas Schwab
2015-04-10 17:13 ` Dmitry Gutov
2015-04-12 23:30 ` Paul Eggert [this message]
2015-04-13 3:03 ` Stefan Monnier
2015-04-14 2:16 ` Dmitry Gutov
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=552AFFF9.90501@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=20290@debbugs.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).