unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, tealeg@member.fsf.org, emacs-devel@gnu.org
Subject: Re: visualization of CVS commits
Date: Fri, 27 Jun 2008 11:08:22 +0200	[thread overview]
Message-ID: <85k5gbdz3t.fsf@lola.goethe.zz> (raw)
In-Reply-To: <uhcbfdzx3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Jun 2008 11:50:48 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Richard M Stallman <rms@gnu.org>
>> CC: tealeg@member.fsf.org, emacs-devel@gnu.org
>> Date: Thu, 26 Jun 2008 17:21:20 -0400
>> 
>>     Why not?  I thought a format was only bad if its details were kept
>>     secret.
>> 
>> A format is bad if it pressures people into use of non-free software.
>> Secrecy is one reason that might happen, but patents are another.
>> Rapid changes by a company are another.  Those two both apply to Flash.
>
> Are there pattern issues with MS Word format?

I think partly so.

> And if so, how come OpenOffice handles it without risking litigation?

Sun has a patent exchange pact with Microsoft.  I think this would tend
to cover the upstream OpenOffice and thus keep the topic off the table.
Microsoft tends to apply visible pressure only when they consider
something at stake for them, so they tend to be rather lax about
pursuing reverse engineering of their formats and the usage (keeps the
focus off the possible consequences of their monopoly position).  You
can't rely on it: it has surprised a lot of people when they started
pursuing some FAT patent for preformatted media recently.

But Openoffice derivatives are off the radar in that respect, I guess.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum




  reply	other threads:[~2008-06-27  9:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  6:01 visualization of CVS commits Werner LEMBERG
2008-06-24 17:37 ` Richard M Stallman
2008-06-24 19:29   ` Paul R
2008-06-25 15:24     ` Richard M Stallman
2008-06-25 15:38       ` David Kastrup
2008-06-25 15:44         ` Geoffrey Teale
2008-06-25 17:37           ` David Kastrup
2008-06-25 20:50             ` James Cloos
2008-06-25 23:26               ` Thomas Lord
2008-06-26 21:21                 ` Richard M Stallman
2008-06-26  7:47             ` Geoffrey Teale
2008-06-25 17:38           ` Eli Zaretskii
2008-06-25 18:36             ` David Kastrup
2008-06-26 21:21             ` Richard M Stallman
2008-06-27  8:50               ` Eli Zaretskii
2008-06-27  9:08                 ` David Kastrup [this message]
2008-06-27 15:38                 ` Richard M Stallman
2008-06-25 17:12         ` Stefan Monnier
2008-06-26 21:21         ` Richard M Stallman
2008-06-25 17:07       ` Paul R
2008-06-26 21:21         ` Richard M Stallman
2008-06-27  0:47           ` Stephen J. Turnbull
2008-06-27  1:13             ` Nick Roberts
2008-06-27  1:35             ` Thomas Lord
2008-06-27 15:38               ` Richard M Stallman
2008-06-27 19:56                 ` Thomas Lord
2008-06-28 13:20                   ` Richard M Stallman
2008-06-27  6:09             ` David Kastrup
2008-06-27  7:26             ` Paul R
2008-06-27 15:38             ` Richard M Stallman
2008-06-27  6:32           ` tomas
2008-06-27 15:38             ` Richard M Stallman
2008-06-27 19:48               ` Thomas Lord

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=85k5gbdz3t.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=tealeg@member.fsf.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).