From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Best way to get hang of an elisp file?
Date: Sat, 16 Nov 2013 11:06:30 -0500 [thread overview]
Message-ID: <jwv1u2g2vbk.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 87vbztohre.fsf@gmail.com
> I would like to compare the two elisp libraries, BBDB 2 and BBDB 3, for
> copyright purposes and would appreciate any other suggestions that'll
> aid a plebe such as myself in the endeavor.
> How to differentiate, for instance, Jamie's work from Roland's work?
That can be fairly difficult, indeed.
The way I do it, usually, is to look at all the commits by authors for
whom we don't have copyright papers yet. I group them by author.
For all authors whose sum of commits is small enough to be considered
"trivial", we don't need paperwork, so I take them out.
For all remaining authors, I look at all their commits and try to track
that code's subsequent life, to see if it has been removed/overwritten
and figure out where it can still be found in the latest version of
the code (in case it was moved, reindented, ...).
In the case of BBDB, this is rather difficult because Jamie's code is
fairly large, so it's a lot of work to track his code through all of
Roland's changes to see what remains.
So I think we'd need to use some other approach. E.g. Roland should be
able to give us some important indications like "all this file is only
mine", "all that file was completely rewritten".
Stefan
next prev parent reply other threads:[~2013-11-16 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 16:52 Best way to get hang of an elisp file? Marcin Borkowski
2013-10-18 17:22 ` Thorsten Jolitz
2013-10-18 21:42 ` Drew Adams
2013-10-19 1:32 ` Stefan Monnier
2013-10-19 2:22 ` Drew Adams
2013-11-15 14:35 ` Sean Sieger
2013-11-16 16:06 ` Stefan Monnier [this message]
2013-11-18 20:40 ` Sean Sieger
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=jwv1u2g2vbk.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.