Gnus development mailing list
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	luis fernandes <elf@ee.ryerson.ca>,
	ding@gnus.org
Subject: Re: copyrights to be fixed
Date: Wed, 14 Feb 2007 22:17:52 -0500	[thread overview]
Message-ID: <17875.53472.944753.639764@fencepost.gnu.org> (raw)
In-Reply-To: <v9tzxofpmc.fsf@marauder.physik.uni-ulm.de>


Reiner Steib wrote (on Wed, 14 Feb 2007 at 21:31 +0100):

> The file etc/images/README (in Gnus CVS) describes the origin of the
> new Gnome-style icons in detail.

Thanks, I used it to improve the various etc/images/README files in
Emacs.

> If considered useful, this file could be installed and synched in
> Emacs CVS, e.g. as `etc/images/README.gnus' (just ask Miles Bader to
> sych it).

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.

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.

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).




  reply	other threads:[~2007-02-15  3:17 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 [this message]
2007-02-15 19:52                                 ` Reiner Steib
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=17875.53472.944753.639764@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    --cc=elf@ee.ryerson.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. 
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).