unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA-diffs] /srv/bzr/emacs/elpa r312: Update AUCTeX ELPA package to the new 11.87 release.
Date: Tue, 04 Dec 2012 08:29:36 +0100	[thread overview]
Message-ID: <87fw3m1di7.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <jwvobiax59k.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 03 Dec 2012 15:40:32 -0500")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

> I have some questions about copyright in your latest AUCTeX update.
>
> What is the copyright status of the following new files:
>
> - psfig.el, epsf.el, latexinfo.el (Gemis is not found in copyright.list)?
> - dinbrief.el (Werner Fink is not found in copyright.list)?
> - prosper.el (Philippe Lord has papers on file for Emacs, but Nevin
>   Kapur only for Gnus)?

Oh, sorry.  I'll investigate on those and try to get the CAs.  I didn't
check the status for them, because we only accept contributions
including CAs nowadays, but maybe those are old leftovers...

For the time being, I've delete the files from the elpa branch.

> Also why change copyright from FSF to Hidenobu Nabetani in tex-jp.el:
>
>    -;; Copyright (C) 1999, 2001-2007, 2012  Free Software Foundation, Inc.
>    +;; Copyright (C) 1999, 2001 Hidenobu Nabetani <nabe@debian.or.jp>
>    +;; Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation
>
> -- Stefan "Who just shortened some copyright year ranges in `elpa'"

I didn't really merge elpa/packages/auctex with the auctex CVS
repository (which is not so easy because the directory layout differs)
but just copied over the files from the new auctex release tarball.  But
now I'm going to merge your copyright header changes back to the auctex
CVS.

Bye,
Tassilo



  reply	other threads:[~2012-12-04  7:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1TfF2V-0003Gn-No@vcs.savannah.gnu.org>
2012-12-03 20:40 ` [ELPA-diffs] /srv/bzr/emacs/elpa r312: Update AUCTeX ELPA package to the new 11.87 release Stefan Monnier
2012-12-04  7:29   ` Tassilo Horn [this message]
2012-12-04 14:50     ` Stefan Monnier
2012-12-04 20:34       ` Tassilo Horn
2012-12-04 21:26         ` Stefan Monnier
2012-12-05 14:06           ` Tassilo Horn
2012-12-05 14:24             ` David Kastrup
2012-12-05 14:39               ` [AUCTeX-devel] " Uwe Brauer
2012-12-05 15:14               ` Stefan Monnier
2012-12-05 16:46                 ` David Kastrup
2012-12-05 17:22                   ` [AUCTeX-devel] " Didier Verna
2012-12-05 18:36                   ` Stefan Monnier
2012-12-06  1:46                 ` Stephen J. Turnbull
2012-12-15 14:08               ` Tassilo Horn
2012-12-08 11:25             ` [AUCTeX-devel] " Ralf Angeli

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=87fw3m1di7.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --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).