From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Seeing which commits modified a range of lines?
Date: Sat, 08 Nov 2014 09:26:04 +0100 [thread overview]
Message-ID: <87d28yp083.fsf@zigzag.favinet> (raw)
In-Reply-To: <loom.20141107T223919-220@post.gmane.org> (Tom's message of "Fri, 7 Nov 2014 21:42:02 +0000 (UTC)")
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
() Tom <adatgyujto@gmail.com>
() Fri, 7 Nov 2014 21:42:02 +0000 (UTC)
If you have a longer function which is modified a lot
of times and you are interested in a chunk of code in
it and want to see only its modifications then a
feature which can pinpoint the modifications in the
chunk can be much more useful than grepping the
changelog.
No doubt. I address only the quality of the usefulness,
not its quantity, which (due to its Quality component) is
necessarily pov-specific. My message was a semi-bitter
grousing response to the "I am surprised" bit, that's all.
[Insert nothing-gold-can-stay long-hair laments, here. :-D]
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-11-08 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 20:13 Seeing which commits modified a range of lines? Tom
2014-11-05 8:37 ` Tassilo Horn
2014-11-05 20:30 ` Tom
2014-11-06 7:13 ` Tassilo Horn
2014-11-06 20:46 ` Tom
2014-11-07 7:53 ` Thien-Thi Nguyen
2014-11-07 21:42 ` Tom
2014-11-08 8:26 ` Thien-Thi Nguyen [this message]
[not found] <mailman.12815.1415132057.1147.help-gnu-emacs@gnu.org>
2014-11-04 22:36 ` Stefan Monnier
2014-11-05 20:27 ` Tom
2014-11-05 22:31 ` Stefan Monnier
2014-11-06 20:56 ` Tom
[not found] ` <mailman.13069.1415307407.1147.help-gnu-emacs@gnu.org>
2014-11-06 22:42 ` Stefan Monnier
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=87d28yp083.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@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 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.