From: Richard Riley <rileyrg@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Automatically commenting changes
Date: Wed, 26 Jan 2011 14:57:26 +0100 [thread overview]
Message-ID: <ihp986$9kj$1@quimby.gnus.org> (raw)
In-Reply-To: mailman.0.1296048116.12534.help-gnu-emacs@gnu.org
Gary <help-gnu-emacs@garydjones.name> writes:
> Stefan Monnier wrote:
>
>>> An editor I used long long ago had the ability to tag lines you
>> changed
>>> with your name (or some other customisable character sequence). For
>>> example if I changed the line
>>> int i = 0;
>>> the editor would automatically generate a comment on the end:
>>> int i = 1; /*gary*/
>
>> I think the way to attack such a problem nowadays is to keep your code
>> in a version control system (VCS), which then keeps track of all that
>> info for you.
>
> I do. But before I commit, or rather in the process of commiting, when
> there is the original file I branched from to consider, plus my changes,
> possibly plus changes from others who have commited since I branched,
> things can get confusing.
>
> For example, if I see as a difference the above "int i = 1" instead of
> "0", I only know it is different to what it was - did I change it? Did
> someone else? If I did, does it really make sense, or was it just
> something I did in order to achieve some debugging purpose? If I can at
> least easily see that it is one of my changes, I have a chance of
> understanding why I did it.
>
git-blame
magit
next prev parent reply other threads:[~2011-01-26 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1295948439.29299.help-gnu-emacs@gnu.org>
2011-01-25 10:09 ` Automatically commenting changes Pascal J. Bourguignon
2011-01-26 3:32 ` Stefan Monnier
2011-01-26 13:21 ` Gary
[not found] ` <mailman.0.1296048116.12534.help-gnu-emacs@gnu.org>
2011-01-26 13:57 ` Richard Riley [this message]
2011-01-26 16:05 ` Gary
[not found] ` <mailman.2.1296057926.30134.help-gnu-emacs@gnu.org>
2011-01-26 19:54 ` Tim X
2011-01-27 2:16 ` Stefan Monnier
2011-01-26 15:55 ` Stefan Monnier
2011-01-25 9:40 Gary
2011-01-25 9:46 ` Deniz Dogan
2011-01-25 10:48 ` Gary
2011-01-25 18:38 ` Thierry Volpiatto
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='ihp986$9kj$1@quimby.gnus.org' \
--to=rileyrg@googlemail.com \
--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.
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).