From: Dmitry Gutov <dgutov@yandex.ru>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
25105@debbugs.gnu.org, npostavs@users.sourceforge.net,
Stefan Monnier <monnier@iro.umontreal.ca>,
Dima Kogan <dima@secretsauce.net>
Subject: bug#25105: M-p in diff-mode jumps too far
Date: Wed, 18 Jan 2017 02:24:43 +0300 [thread overview]
Message-ID: <9dba6552-cd54-c6f0-18de-6822d43b0944@yandex.ru> (raw)
In-Reply-To: <alpine.DEB.2.20.1701161514330.7787@calancha-pc>
On 16.01.2017 09:26, Tino Calancha wrote:
> OK, below is my draft for the second commit.
> Please don't hesitate to send me comments to make it more clear or/and
> fix some broken grammar.
Here's a fresh idea. If we're not going to worry about (not) showing
Dima's commit message in the generated change log, maybe the new message
should talk about tweaking the code, and not retell the original message.
Or the users will read it twice, basically. But only those users that
read change logs, of course.
next prev parent reply other threads:[~2017-01-17 23:24 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
2017-01-14 5:47 ` Tino Calancha
2017-01-16 6:26 ` Tino Calancha
2017-01-17 23:24 ` Dmitry Gutov [this message]
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=9dba6552-cd54-c6f0-18de-6822d43b0944@yandex.ru \
--to=dgutov@yandex.ru \
--cc=25105@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
--cc=npostavs@users.sourceforge.net \
--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).