From: Andreas Schwab <schwab@linux-m68k.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 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: Fri, 10 Apr 2015 17:55:56 +0200 [thread overview]
Message-ID: <87lhi0gepf.fsf@igel.home> (raw)
In-Reply-To: <5527C17E.1040404@yandex.ru> (Dmitry Gutov's message of "Fri, 10 Apr 2015 15:26:38 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> Which signals that users prefer, or at least are more used to, unified
> diffs. I've recently wanted to show off the "refinement" diff-mode feature
> to a colleague, and that stumbled on Emacs producing a context diff by
> default,
The refinement works well with context diffs.
> And here I disagree: unified diffs are easier, because they clearly show
> you the changes. You don't need to compare the "before" and "after" in
> your head, to figure out what exactly changed.
That's where the refinement helps in the same way as with unified diffs.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-04-10 15:55 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 [this message]
2015-04-10 17:13 ` Dmitry Gutov
2015-04-12 23:30 ` Paul Eggert
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=87lhi0gepf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=20290@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).