unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Adrian Robert <Adrian.B.Robert@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: nextstep copyright issues
Date: Wed, 16 Jul 2008 13:23:49 -0400	[thread overview]
Message-ID: <rby741g2u2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <loom.20080716T115317-194@post.gmane.org> (Adrian Robert's message of "Wed, 16 Jul 2008 12:05:58 +0000 (UTC)")

Adrian Robert wrote:

> All three of them should be on file.

I'll ask fsf-records.

> This is correct, except for Adam Ratcliffe <adam@prema.co.nz>,
> who wrote the Preferences Panel section of ns-emacs.texi.  I am
> not sure whether he signed papers or not.

I will ask.

> Steve Nygard worked on unexnext.c. 

I see his assignment now.

>> nextstep/GNUstep/Emacs.base/Resource/emacs.tiff should have a
>> README like those in etc/images.  (Does this file need to be
>> here rather than in etc/images?)
>
> It does not need to be there I guess, but it followed the convention
> for nextstep/Cocoa/Emacs.base/Contents/Resources/Emacs.icns, which
> in turn followed the Carbon port
> mac/Emacs.app/Contents/Resources/Emacs.icns. All three are the icon
> used for Emacs. Keeping them there keeps the app packaging support
> structure consolidated and avoids the need for extra code in the
> Makefile to copy them separately.

Fine. Can you add a README as per etc/images then?

The mac directory with the *.icns should have one too.




  parent reply	other threads:[~2008-07-16 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  3:04 nextstep copyright issues Glenn Morris
2008-07-16 12:05 ` Adrian Robert
2008-07-16 12:25   ` Miles Bader
2008-07-16 17:23   ` Glenn Morris [this message]
2008-07-17 16:51     ` Glenn Morris
2008-07-17 19:02       ` Adrian Robert

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=rby741g2u2.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=Adrian.B.Robert@gmail.com \
    --cc=emacs-devel@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 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).