all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fren Zeee <frenzeee@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Harald Hanche-Olsen <hanche@math.ntnu.no>, emacs-devel@gnu.org
Subject: Re: Comment on Emacs Lisp Introduction
Date: Mon, 2 Aug 2010 11:27:34 -0700	[thread overview]
Message-ID: <AANLkTi=sgO6qB+sGZXXZvYmkaa=_YcbaWwQ-soff9b0y@mail.gmail.com> (raw)
In-Reply-To: <87bp9lto70.fsf@uwakimon.sk.tsukuba.ac.jp>

On Mon, Aug 2, 2010 at 1:26 AM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> Harald Hanche-Olsen writes:
>  > + David Kastrup <dak@gnu.org>:
>  >
>  > > Distributing Emacs without corresponding source to the byte code is a
>  > > violation of its license.
>  >
>  > Is it? I thought you only had to offer access to the source code.
>
> Normally you have to offer access to source in the same way as you
> offer access to binaries.  You don't need to bundle them in the same
> medium, but normally they're available more or less side by side.
>
> Under certain circumstances the object code may be conveyed separately
> from the source, but the conditions are pretty onerous (it must be a
> physical product, and it must be accompanied with a paper certificate
> promising that *anybody* with a copy of the object code can get it
> from you); it's unlikely that the OP received his code that way.
>
> I'm less than impressed with the OP's complaints, of course.

I am not complaining. Its just that I dont have it, and need to find
source matching this old executable, which means that it will take
some time to search for the particular freeze or tar file if it is
still on the web.

>
>
>



  reply	other threads:[~2010-08-02 18:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinmXz=n0L4RS0SHRiJcA-Ob135RrKEzrZ=GvjDy@mail.gmail.com>
2010-07-29 22:22 ` Comment on Emacs Lisp Introduction Robert J. Chassell
     [not found]   ` <AANLkTi=SAbC_y+O3simX2dSLFYcpyVxPR-yZYsCMje42@mail.gmail.com>
2010-07-30 14:44     ` Robert J. Chassell
2010-07-31  7:43       ` Fren Zeee
2010-07-31  8:01         ` David Kastrup
2010-07-31 19:33           ` Fren Zeee
2010-07-31 19:34             ` Fren Zeee
2010-07-31 20:06               ` Drew Adams
2010-07-31 20:14               ` Óscar Fuentes
2010-08-01  6:36               ` David Kastrup
2010-08-01 12:06                 ` Harald Hanche-Olsen
2010-08-02  8:26                   ` Stephen J. Turnbull
2010-08-02 18:27                     ` Fren Zeee [this message]
2010-08-03  3:26                       ` Stephen J. Turnbull
2010-08-04  3:19                         ` Fren Zeee
2010-08-04  5:25                           ` Stephen J. Turnbull
2010-08-04  9:22                           ` David Kastrup
2010-08-05 20:13                             ` Fren Zeee
2010-08-05 20:27                               ` Fren Zeee
2010-08-01 12:50                 ` Óscar Fuentes

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='AANLkTi=sgO6qB+sGZXXZvYmkaa=_YcbaWwQ-soff9b0y@mail.gmail.com' \
    --to=frenzeee@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=hanche@math.ntnu.no \
    --cc=stephen@xemacs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.