From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Rצhler" <andreas.roehler@online.de>
Cc: emacs-devel@gnu.org
Subject: Re: No sources for lisp/international/uni-*.el?
Date: Tue, 09 Aug 2011 18:29:33 +0300 [thread overview]
Message-ID: <83hb5qzjqa.fsf@gnu.org> (raw)
In-Reply-To: <4E4100E4.3090705@online.de>
> Date: Tue, 09 Aug 2011 11:41:56 +0200
> From: Andreas Röhler <andreas.roehler@online.de>
> CC: emacs-devel@gnu.org
>
> Am 09.08.2011 10:45, schrieb Eli Zaretskii:
> >> Date: Tue, 09 Aug 2011 10:21:09 +0200
> >> From: Andreas Röhler<andreas.roehler@online.de>
> >>
> >>
> >>> I apologize to the other list members for the tone in this mail.
> >>>
> >>
> >> which pretty good illustrates my concern
> >
> > Tone aside, your repeated attacks on the GPL
>
> Hi Eli,
>
> even if my contributions are modest, it should be clear I'm a supporter
> of free software. BTW published several stuff under GPL.
That's besides the point in this case.
> I'm far from attacking.
Then perhaps your wording needs to be revised, because any time
related issues come up, your messages are explicitly negative.
> OTOH should I hide concern if envisaging danger, which might destroy the
> whole project still, if not faced?
This is not the place to express those concerns, that's all I'm
saying. There are other forums for that. Why you insist talking
about this here is beyond me.
next prev parent reply other threads:[~2011-08-09 15:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 7:35 [23.0.90] No sources for lisp/international/uni-*.el? Ulrich Mueller
2009-02-02 8:03 ` Glenn Morris
2009-02-02 10:33 ` Ulrich Mueller
2011-08-07 18:04 ` Ulrich Mueller
2011-08-08 0:29 ` Richard Stallman
2011-08-08 5:56 ` Ulrich Mueller
2011-08-08 8:14 ` David Kastrup
2011-08-09 1:44 ` Richard Stallman
2011-08-09 5:07 ` David Kastrup
2011-08-10 0:25 ` Richard Stallman
2011-08-10 16:01 ` Chong Yidong
2011-08-10 16:38 ` Eli Zaretskii
2011-08-10 16:46 ` Chong Yidong
2011-08-10 16:50 ` Eli Zaretskii
2011-08-10 16:58 ` Chong Yidong
2011-08-10 17:19 ` Eli Zaretskii
2011-08-10 17:36 ` Chong Yidong
2011-08-10 17:41 ` Eli Zaretskii
2011-08-10 17:48 ` Chong Yidong
2011-08-10 18:08 ` Eli Zaretskii
2011-08-10 17:39 ` Eli Zaretskii
2011-08-11 17:45 ` Richard Stallman
2011-08-11 18:24 ` Chong Yidong
2011-08-11 17:45 ` Richard Stallman
2011-08-11 20:18 ` Chong Yidong
2011-08-12 17:56 ` Richard Stallman
2011-08-12 18:05 ` Eli Zaretskii
2011-08-09 7:10 ` Andreas Röhler
2011-08-09 8:02 ` David Kastrup
2011-08-09 8:21 ` Andreas Röhler
2011-08-09 8:45 ` Eli Zaretskii
2011-08-09 9:41 ` Andreas Röhler
2011-08-09 15:27 ` Thien-Thi Nguyen
2011-08-09 15:29 ` Eli Zaretskii [this message]
2011-08-09 9:59 ` Ulrich Mueller
2011-08-09 14:13 ` Stephen J. Turnbull
2011-08-09 15:26 ` Eli Zaretskii
2011-08-10 0:23 ` Richard Stallman
2011-08-11 17:45 ` Richard Stallman
2011-08-08 2:04 ` Stephen J. Turnbull
2011-08-08 4:32 ` Eli Zaretskii
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=83hb5qzjqa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--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).