Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Glenn Morris <rgm@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	luis fernandes <elf@ee.ryerson.ca>,
	ding@gnus.org, Bill Wohler <wohler@newt.com>
Subject: Re: copyrights to be fixed
Date: Thu, 15 Feb 2007 20:52:00 +0100	[thread overview]
Message-ID: <v964a3nqqn.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <17875.53472.944753.639764@fencepost.gnu.org> (Glenn Morris's message of "Wed\, 14 Feb 2007 22\:17\:52 -0500")

On Thu, Feb 15 2007, Glenn Morris wrote:

> I don't think we need to add it to Emacs, partly because it duplicates
> information already there (in various separate README files), partly
> because it refers to images which are not in Emacs (yet?), which might
> be confusing.

I'd expect all images from Gnus (v5-10 = stable branch) mentioned in
Gnus to be present in Emacs as well.

> But this means it will be necessary to remember to transfer the
> information to the Emacs README files when a Gnus update changes the
> icons in Emacs.

Yes.

> The Gnus README does not describe the copyright or license details of
> the various icons files (compare with the READMEs in Emacs etc/images/
> directories).

Sorry, the README file only contains information about the recently
(in 2006) added images, not about the old ones.

WRT separator.xpm: I originally used the file from AUCTeX ...

2006-02-21  Miguel Frasson  <frasson@math.leidenuniv.nl>

	* etc/images/separator.xpm: Copy of sep.xpm from AUCTeX.

... but later Bill Wohler (ex?)changed it as described in
etc/ChangeLog.  Bill?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2007-02-15 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3ps8tmg3e.fsf@localhost.localdomain>
     [not found] ` <E1HD59v-0001fH-BW@fencepost.gnu.org>
     [not found]   ` <uk5yz1p2z.fsf@gnu.org>
     [not found]     ` <E1HDTbY-0001mk-6t@fencepost.gnu.org>
     [not found]       ` <uveiizhur.fsf@gnu.org>
     [not found]         ` <E1HDrd0-0002te-AE@fencepost.gnu.org>
     [not found]           ` <34ps8nirvt.fsf@fencepost.gnu.org>
     [not found]             ` <nylkjbipni.fsf@fencepost.gnu.org>
     [not found]               ` <87irecmhsv.fsf@stupidchicken.com>
     [not found]                 ` <17870.29230.484784.159058@fencepost.gnu.org>
     [not found]                   ` <873b5chd1g.fsf@stupidchicken.com>
     [not found]                     ` <17871.26334.452405.11637@fencepost.gnu.org>
2007-02-12  0:17                       ` Chong Yidong
2007-02-12  1:35                         ` luis fernandes
2007-02-12  1:55                           ` Chong Yidong
2007-02-14 20:31                             ` Reiner Steib
2007-02-15  3:17                               ` Glenn Morris
2007-02-15 19:52                                 ` Reiner Steib [this message]
2007-02-15 21:58                                   ` Glenn Morris
2007-02-16 19:54                                     ` Reiner Steib
2007-02-18  6:40                                   ` Bill Wohler

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=v964a3nqqn.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    --cc=elf@ee.ryerson.ca \
    --cc=rgm@gnu.org \
    --cc=wohler@newt.com \
    /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 NNTP newsgroup(s).