From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: alinsoar@voila.fr
Cc: "Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: Report the evolution of Emacs Lisp sources.
Date: Tue, 19 Aug 2008 15:22:34 +0200 [thread overview]
Message-ID: <87y72ti1gl.fsf@ambire.localdomain> (raw)
In-Reply-To: <9395796.5994681219054485773.JavaMail.www@wwinf4609> (A. Soare's message of "Mon, 18 Aug 2008 12:14:45 +0200 (CEST)")
() A Soare <alinsoar@voila.fr>
() Mon, 18 Aug 2008 12:14:45 +0200 (CEST)
Yes, it could generate a simple prototype for change logs... as
application. When you cut, add, or modify an old structure it
will immediately see that.
The analysis described in the paper you referenced is very
superficial compared to what is possible w/ elisp. For example,
you can use byte-compiler properties (e.g., no side-effects) to
report the safety of a change.
But note that if you work on version X from the day x, you must
keep the original from the day x, otherwise it will detect in
your report the changes made by others!
Actually, reporting the changes made by others is exactly what i
had in mind. Sometimes what people write in ChangeLog files is
better understood w/ a little help from a "second opinion".
thi
next prev parent reply other threads:[~2008-08-19 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 10:14 Report the evolution of Emacs Lisp sources A Soare
2008-08-19 13:22 ` Thien-Thi Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-20 20:53 A Soare
2008-08-21 2:02 ` Thien-Thi Nguyen
2008-08-20 11:46 A Soare
2008-08-20 20:14 ` Thien-Thi Nguyen
2008-08-19 20:13 A Soare
2008-08-18 7:05 A Soare
2008-08-18 7:05 A Soare
2008-08-18 9:44 ` Thien-Thi Nguyen
2008-08-18 10:05 ` Miles Bader
2008-08-19 13:11 ` Thien-Thi Nguyen
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=87y72ti1gl.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=alinsoar@voila.fr \
--cc=emacs-devel@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 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).