public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners Inc)" <lhall@rfk.com>
To: "Gary R. Van Sickle" <tiberius@braemarinc.com>,
	"gnu-win32@cygnus.com" <gnu-win32@cygnus.com>
Subject: RE: Why text=binary mounts
Date: Fri, 09 Jan 1998 13:40:00 -0000	[thread overview]
Message-ID: <3.0.5.32.19980109111148.00a46e40@pop.ma.ultranet.com> (raw)
In-Reply-To: <01BD1C69.BBA294A0.tiberius@braemarinc.com>

At 07:15 PM 1/8/98 -0600, Gary R. Van Sickle wrote:
>Let me address one sure-to-come-up complaint right now: the notion that it 
>would be too much work to 'fix' all the existing code.  How much time and 
>effort is wasted on 'working around' the current situation?  Certainly more 
>time than it would take to search-and-replace "w" with "wt", etc.

OK, you've come up with yet ANOTHER solution to this problem.  You wouldn't
be the first or probably the last.  So what are YOU going to do about it?  
You raise the issue that the "fix" is generally "dismissed" as a result of 
being too much "work".  From my perspective, the people with this view 
probably agree with the notion that the "fix" must occur but they have found 
work-arounds for their particular environments which are suitable and don't 
require much personal time investment.  Those people who have not and need 
something else complain loudly but seem just as unwilling to take on the 
herculean task.  For the moment, this is still largely a GNU-cenric project 
in spirit, without a large, committed development team behind it.  That said,
let's all acknowledge that while the users of this software may agree in 
general that a particular course of action may be beneficial, unless people 
VOLUNTEER to undertake the task, changes are NOT going to happen quickly.  I
personally don't feel like I've invested any large amount of time to work-
around my text/binary issues, although I don't have many.  Certainly it 
doesn't add up to anywhere near the time investment that would be necessary 
for me to go into even some of the source of these tools and make changes to
alleviate the difficulties.  Certainly one could argue that collectively all
users have spent some significant time working out these issues for themselves
and that maybe if that time was spent, collectively and in an organized 
fashion, fixing the tools, we'd all benefit.  However, as I said, unless 
someone organizes a volunteer effort, things aren't going to change quickly. 
So, if someone wants to pick up and organize that effort, great.  MAYBE I'd
even be willing to help.  However, I'm not certain that having all sorts 
of individuals posting to this list with general algorithms for fixing the
problem is useful, unless the one who posts actually might entertain the 
thought of making the changes, organizing a group to do so, or maybe even
somehow sponsoring Cygnus to do it for them.  I'm not trying to downplay the
issue here and I certainly don't want to discourage people from discussing
issues and solutions.  But this particular issue comes up frequently and 
always ends up being debated in a vacuum.  Admonishing others on this list or
the list in general for not fixing problems one finds intolerable in the 
current software is unfair.  Its not productive.  Perhaps we can find a 
different approach in regard to dealing with the text/binary issue and 
others like it?  I can see some overall benefit from this.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      (781) 239-1053
8 Grove Street                          (781) 239-1655 - FAX
Wellesley, MA  02181                             
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1998-01-09 13:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-08 17:20 Gary R. Van Sickle
1998-01-09 13:40 ` Larry Hall (RFK Partners Inc) [this message]
1998-01-09 13:40 ` Tomas Fasth
1998-01-11 23:40   ` Fergus Henderson
1998-01-12  5:03     ` Tomas Fasth
1998-01-12  4:45       ` Fergus Henderson
1998-01-12 17:26   ` Guy Gascoigne - Piggford
  -- strict thread matches above, loose matches on Subject: below --
1998-01-15 15:16 Gary R. Van Sickle
1998-01-17 23:47 ` Fergus Henderson
1998-01-15 15:16 Richard Thomas
1998-01-18 16:07 ` Steven R. Newcomb
1998-01-15  7:26 Immanuel Litzroth
1998-01-13 10:42 Gary R. Van Sickle
1998-01-15  7:26 ` Peter Dalgaard BSA
1998-01-17 11:00 ` John A. Turner
1998-01-12 14:09 Gary R. Van Sickle
1998-01-14  3:39 ` Richard Thomas
1998-01-16  2:56   ` Jeffrey C. Fried
1998-01-19 10:32     ` Guy Gascoigne - Piggford
1998-01-16  2:56 ` Benjamin Riefenstahl
1998-01-12 10:42 marcus
1998-01-13 10:53 ` Benjamin Riefenstahl
1998-01-12  9:17 marcus
1998-01-10  6:19 Tony Pires
1998-01-10 13:49 ` Christopher Faylor
1998-01-09 18:22 Gary R. Van Sickle
1998-01-12 20:11 ` Guy Gascoigne - Piggford
1998-01-09 18:22 Gary R. Van Sickle
1998-01-12  2:57 ` Benjamin Riefenstahl
1998-01-09 18:22 Gary R. Van Sickle
1998-01-11 10:01 ` Tomas Fasth
1998-01-08  8:31 marcus
1998-01-09  5:51 ` Benjamin Riefenstahl

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=3.0.5.32.19980109111148.00a46e40@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=gnu-win32@cygnus.com \
    --cc=tiberius@braemarinc.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).