unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Question about todos.el copyright and author headers
Date: Tue, 18 Jun 2013 00:33:04 +0200	[thread overview]
Message-ID: <87y5a85pwf.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <jwv8v28st4e.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 17 Jun 2013 10:39:40 -0400")

On Mon, 17 Jun 2013 10:39:40 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>>> I thought the plan was to install your code as todo-mode.el (not
>>> todos-mode.el).
>> There were three plans I asked about: (1) "simply replace the old
>> version", (2) "install the new version alongside the old version", and
>> (3), which you said you favored:
>
> I misread.  What I want is to install the new code as todo-mode.el and
> move the old code to obsolete.

Ok.

>> It's fine with me to keep the name todo-mode.el for the new version and
>> use the "todo-" prefix, but then doesn't the obsoleted version have to
>> be renamed and re-prefixed?
>
> There are many different options for the old code.
> I think the simplest is to rename the file to obsolete/otodo-mode.el
> (but keep the same "todo-*" names in it).

Ok.

>> Or is the idea not to be able to have both versions loaded at the same
>> time, but to be able to switch between them?
>
> As discussed, I think it's OK if users can't use both at the same time.
> It's better if they can, tho, but I'm not sure it's worth the trouble.

Ok.

I'll make the changes and install the new code in the next couple of
days.  If possible, I'll install the accompanying Info file at the same
time, but if that takes me longer to prepare, I'll go ahead with the
code first.

For the ChangeLog and the bzr log, is it sufficient to just write
something like "Update to new version, reimplementing or abandoning
almost all old code and adding much new code." or should I individually
list all reimplemented, removed and new functions, etc.?

Steve Berman



  reply	other threads:[~2013-06-17 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 22:53 Question about todos.el copyright and author headers Stephen Berman
2013-06-17  0:45 ` Stefan Monnier
2013-06-17  8:13   ` Stephen Berman
2013-06-17 14:39     ` Stefan Monnier
2013-06-17 22:33       ` Stephen Berman [this message]
2013-06-18  0:52         ` Stefan Monnier
2013-06-20 14:59       ` Stephen Berman
2013-06-20 20:26         ` 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

  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=87y5a85pwf.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).