all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Dima Kogan <dima@secretsauce.net>, npostavs@users.sourceforge.net
Cc: Mark Oteiza <mvoteiza@udel.edu>, 25105@debbugs.gnu.org
Subject: bug#25105: 26.0.50; diff navigation is broken
Date: Mon, 5 Dec 2016 17:53:41 +0200	[thread overview]
Message-ID: <ba8ea7e6-1099-50fe-f8e0-1bc5e42e6578@yandex.ru> (raw)
In-Reply-To: <87a8cafksc.fsf@secretsauce.net>

On 05.12.2016 17:38, Dima Kogan wrote:

> Hi. These are intentional. Justification:

Which are intentional? I've described some legitimate problems in the 
emacs-devel email.





  reply	other threads:[~2016-12-05 15:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04 15:13 bug#25105: 26.0.50; diff navigation is broken Mark Oteiza
2016-12-04 15:27 ` npostavs
2016-12-05 15:38   ` Dima Kogan
2016-12-05 15:53     ` Dmitry Gutov [this message]
2016-12-05 16:33       ` Dima Kogan
2016-12-05 16:55         ` Mark Oteiza
2016-12-05 17:49           ` Dima Kogan
2016-12-25  6:57             ` Dima Kogan
2016-12-25 13:54               ` Mark Oteiza
2017-01-06  1:14 ` Tino Calancha
2017-01-06  1:20   ` Dima Kogan
2017-01-06  1:27     ` Dima Kogan
2017-01-06  3:06       ` Mark Oteiza
2017-01-06  3:50         ` Tino Calancha
2017-01-06  4:16         ` Dima Kogan
2017-01-06  4:43           ` Mark Oteiza
2017-01-06  7:55           ` Eli Zaretskii
2017-01-06  8:03             ` Tino Calancha
2017-01-06 14:14               ` Dmitry Gutov
2017-01-07  1:54                 ` Tino Calancha
2017-01-07  2:05                   ` Mark Oteiza
2017-01-07  9:51                 ` Dima Kogan
2017-01-07 11:16                   ` Tino Calancha
2017-01-07 22:16                     ` Dima Kogan
2017-01-07 22:27                       ` Dmitry Gutov
2017-01-06  3:09     ` Mark Oteiza
2017-01-06  4:22     ` Tino Calancha

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=ba8ea7e6-1099-50fe-f8e0-1bc5e42e6578@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=25105@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    --cc=mvoteiza@udel.edu \
    --cc=npostavs@users.sourceforge.net \
    /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.