public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bernard Dautrevaux <Dautrevaux@microprocess.com>
To: 'Earnie Boyd' <earnie_boyd@yahoo.com>,
	"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>,
	cygwin@sources.redhat.com
Subject: RE: AW: AW: AW: documentation archive
Date: Thu, 21 Dec 2000 06:20:00 -0000	[thread overview]
Message-ID: <17B78BDF120BD411B70100500422FC6309E1A1@IIS000> (raw)

> -----Original Message-----
> From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> Sent: Wednesday, December 20, 2000 5:11 PM
> To: Larry Hall (RFK Partners, Inc); cygwin@sources.redhat.com
> Subject: RE: AW: AW: AW: documentation archive
> 
> 
> --- "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
> > At 10:49 AM 12/20/2000, Earnie Boyd wrote:
> > >--- Bernard Dautrevaux <Dautrevaux@microprocess.com> wrote:
> > > > Why not switch to the quite common ".tgz" suffix 
> instead of .tar.gz" and
> > > > replace dots in release numbers by underscores? this 
> could be done almost
> > > > unambiguously (at least as long as package names do not 
> contain '-'):
> > > > 
> > >
> > >Yuck!!  Not worth it.
> > 
> > 
> > I'm not sure I understand this reaction.  To be honest, I 
> think simple 
> > permutation in form that addresses the inevitable queries 
> to the list 
> > regarding the problem of name-mangling by browsers a "good 
> thing"(tm) (of 
> > course one could argue that the browsers need to be 
> fixed!;-)).  This idea 
> > seems to be focused toward that goal.  Logistics of making 
> this change aside,
> > 
> > is there a reason this would NOT be a good idea?  Just curious...
> > 
> 
> Yes, the browsers should be fixed and the most recent version 
> of Netscape
> Communicator doesn't mangle the names any more.  There are 
> other reasons
> besides name mangling, such as, file content mangling that 
> alwo happens.  If
> the browser doesn't understand the extention then it 
> downloads in text mode. 
> So, it's not worth changing the name.

Are you sure of that ? I was thinking that unrecognized files were always
transfered as binary data and BTW, I'm not sure that IE5 has any knowledge
of a '.gz' suffix :-)

Note that as windows FTP client are concerned they effectively try to use
the suffix to choose between binary and text format while UNIX clients
ususally ALWAYS use text format unless explicitely directed to binary mode
:-)

Regards,

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2000-12-21  6:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-21  6:20 Bernard Dautrevaux [this message]
2000-12-21  8:43 ` Robert Collins
  -- strict thread matches above, loose matches on Subject: below --
2000-12-21  6:14 Bernard Dautrevaux
2000-12-20  8:11 Earnie Boyd
2000-12-20  7:49 Earnie Boyd
2000-12-20  8:02 ` Larry Hall (RFK Partners, Inc)
2000-12-20  5:31 Bernard Dautrevaux
2000-12-20 13:42 ` Jari Aalto+list.cygwin
2000-12-20  3:36 Schaible, Joerg
2000-12-20  4:24 ` Gerrit P. Haase

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=17B78BDF120BD411B70100500422FC6309E1A1@IIS000 \
    --to=dautrevaux@microprocess.com \
    --cc=cygwin@sources.redhat.com \
    --cc=earnie_boyd@yahoo.com \
    --cc=lhall@rfk.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).