From: npostavs@users.sourceforge.net
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
25105@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Dima Kogan <dima@secretsauce.net>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#25105: M-p in diff-mode jumps too far
Date: Fri, 13 Jan 2017 20:49:17 -0500 [thread overview]
Message-ID: <877f5yza02.fsf@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1701131549540.17727@calancha-pc> (Tino Calancha's message of "Fri, 13 Jan 2017 15:54:28 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> writes:
> On Fri, 13 Jan 2017, npostavs@users.sourceforge.net wrote:
>
>> Hmm, I'm still getting duplicates. Maybe I shouldn't have merged? Oh well.
> Could be because i answered the e-mail to you and CC to Bug#25105? If you
> are registered to that bug you might get 2 e-mails.
I think that's the normal case, and usually I don't get duplicated
mails.
>> I was thinking more about this summary line. And maybe add some higher
>> level explanation before the ChangeLog entry about the problems being
>> solved?
> How about copy verbatim the comentary from Dima in 2c8a7e5? He explained
> very clearly the problem, and i am solving the same thing.
> Mention to the regressions should must appear in the previous commit,
> where i do the actual revert.
Yes, that looks good, though if I understand correctly, the important
difference is that the navigation commands are not changed in your
patch, only the manipulation ones, right?
next prev parent reply other threads:[~2017-01-14 1:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 21:21 bug#25400: M-p in diff-mode jumps too far Stefan Monnier
2017-01-08 23:27 ` Mark Oteiza
2017-01-09 4:34 ` Stefan Monnier
2017-01-11 4:38 ` bug#25105: " Tino Calancha
2017-01-11 23:27 ` Mark Oteiza
2017-01-11 23:34 ` Dmitry Gutov
2017-01-12 3:53 ` bug#25400: " Tino Calancha
2017-01-13 3:35 ` Dmitry Gutov
2017-01-13 3:55 ` Tino Calancha
2017-01-14 3:11 ` bug#25105: bug#25400: " Dmitry Gutov
2017-01-21 3:02 ` Tino Calancha
2017-01-23 3:42 ` bug#25105: " Dmitry Gutov
2017-01-13 4:25 ` Tino Calancha
2017-01-13 5:57 ` bug#25105: " npostavs
2017-01-13 6:26 ` Tino Calancha
2017-01-13 6:42 ` bug#25105: " npostavs
2017-01-13 6:54 ` Tino Calancha
2017-01-14 1:49 ` npostavs [this message]
2017-01-14 5:47 ` Tino Calancha
2017-01-16 6:26 ` Tino Calancha
2017-01-17 23:24 ` Dmitry Gutov
2017-01-18 6:11 ` Tino Calancha
2017-01-14 3:16 ` bug#25105: bug#25400: " 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=877f5yza02.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25105@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=dima@secretsauce.net \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
--cc=tino.calancha@gmail.com \
/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).