git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/4] Add a basic test case for git send-email, and fix some real bugs discovered.

From
CFChristopher Faylor <me@cgf.cx>
Date
May 30, 2006, 17:03 UTC
Message-ID
<20060530170306.GA10895@trixie.casa.cgf.cx>
In-Reply-To
<81b0412b0605300900l7530792dqcea6d812602b9176@mail.gmail.com>
On Tue, May 30, 2006 at 06:00:20PM +0200, Alex Riesen wrote:
Show 15 quoted lines
>On 5/30/06, Christopher Faylor <me@cgf.cx> wrote:
>>>froze afterwards anyway, as "wc" or "perl" did. Besides, it the
>>>command often freezes that poor imitation of xterm windows has.
>>
>>I assume that "the poor imitation of xterm" is referring to cygwin's
>>xterm here.  It's really too bad that you can't get into the mindset of
>>reporting problems to the cygwin mailing list when you notice them.
>
>Actually, I was referring to windows console. And no, I don't think you
>could do something about it.
>
>But honestly, I don't think it's worth supporting windows in general
>and cygwin in particular. And before anyone (again) asks why am
>_I_ doing it: I'd have to do my job with Perforce otherwise (as if
>windows wasn't bad enough...)
I think you've made your opinion on this issue pretty clear.
Show 5 quoted lines
>>I can't comment on the proposed patch since, AFAIK, using cat, wc, and
>>(cygwin's) perl should all work just fine but I don't think it is ever
>>correct to complain about a platform in released software.
>
>If you actually read the message, you'd probably notice ActiveState Perl.

I actually did read the message. Do you really want to employ this type of hackneyed usenet technique here?

Referring to the Windows console as "xterm" (if that is what you were actually doing) means that your bug report and patch were unclear.

You were also talking about "cat" and "wc" hanging. Neither is a Windows command. Since you've previously complained that you had to use Cygwin, I think it is safe to assume that you were talking about Cygwin commands.

>I have no idea why have you taken my post as an attempt to insult cygwin;

There you go. Kick it up a notch. I asked you (and have been asking you) to report problems with Cygwin in the Cygwin forums. I don't think that someone mentioning that software has bugs is an "insult". You obviously aren't insulting git by fixing bugs that you find.

>IF I had that in mind I'd dedicate a whole long post just to that.

I could write a really long essay about inappropriate mailing list hostility, too. Neither would be on-topic here, of course.

Anyway, I think that comments should be factual and not contain negative opinions about Windows, Solaris, or whatever.

cgf
Previous: Alex RiesenNext: Ryan Anderson
Message 7 of 10 in “Re: [PATCH 4/4] Add a basic test case for git send-email, and fix some real bugs discovered.”
  1. Junio C HamanoMay 30, 2006
  2. Junio C HamanoMay 30, 2006
  3. Junio C HamanoMay 30, 2006
  4. Alex RiesenMay 30, 2006
  5. Christopher FaylorMay 30, 2006
  6. Alex RiesenMay 30, 2006
  7. Christopher FaylorMay 30, 2006
  8. Ryan AndersonMay 30, 2006
  9. Alex RiesenMay 30, 2006
  10. Ryan AndersonMay 30, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.