Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org, jan.kratochvil@redhat.com, jim@meyering.net
Subject: Re: xz-compressed release tarballs?
Date: Mon, 30 Jan 2012 06:26:00 -0000	[thread overview]
Message-ID: <201201300127.57697.vapier@gentoo.org> (raw)
In-Reply-To: <8362fvxiza.fsf@gnu.org>

[-- Attachment #1: Type: Text/Plain, Size: 1102 bytes --]

On Saturday 28 January 2012 22:53:13 Eli Zaretskii wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > being a free software developer doesn't mean being able to force
> > people to adhere to what works on their personal legacy systems
> > where the user refuses to upgrade the software.  that is
> > unreasonable.
> 
> I cannot and didn't force anyone to do anything.  I made a request.
> Disagreeing with that request and acting against it is entirely
> appropriate and understood; calling it ridiculous or using other
> derogatory language is not.

sorry, but i guess that's my interpretation.  asking people to not use xz even 
though you've shown no reason other than tar itself on deficient platforms 
cannot directly read the compression is ridiculous.  it is absolutely trivial 
to decompress it first if you are on such a system as i showed.

> There's nothing in MS-Windows systems that can be called "legacy" or
> "old".

seriously ?  there is *plenty* in MS-Windows that can be called both those 
things.  even MS documents these in great detail in the MSDN.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-01-30  6:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 20:22 Jim Meyering
2012-01-26 20:32 ` Jan Kratochvil
2012-01-26 21:31   ` Eli Zaretskii
2012-01-26 22:15     ` Jan Kratochvil
2012-01-26 23:10       ` Samuel Bronson
2012-01-27  1:49       ` Mike Frysinger
2012-01-27  9:13         ` Eli Zaretskii
2012-01-27  5:02       ` Joel Brobecker
2012-01-27  9:36         ` Eli Zaretskii
2012-01-30 19:08         ` Tom Tromey
2012-01-27  1:48     ` Mike Frysinger
2012-01-27  9:12       ` Eli Zaretskii
2012-01-27 18:41         ` Mike Frysinger
2012-01-28  8:21           ` Eli Zaretskii
2012-01-28 23:08             ` Mike Frysinger
2012-01-29  3:55               ` Eli Zaretskii
2012-01-30  6:26                 ` Mike Frysinger [this message]
2012-01-30 17:49                   ` Alfred M. Szmidt
2012-01-30 19:54               ` Stan Shebs
2012-01-30 20:53                 ` Pedro Alves
2012-01-30 21:06                 ` Mike Frysinger
2012-01-27  2:37     ` Ralf Corsepius
2012-01-27  9:26   ` Jan Kratochvil
2012-01-27 20:27     ` Mike Frysinger
2012-01-27 20:30       ` Marek Polacek

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=201201300127.57697.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=jim@meyering.net \
    /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