unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: "Miles Bader" <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Info about available CVS/Arch/Git branches
Date: Mon, 20 Aug 2007 11:42:30 +0530	[thread overview]
Message-ID: <e3f230850708192312i41f3ec5ex2dae33d0b0556a41@mail.gmail.com> (raw)
In-Reply-To: <buoir7an8bm.fsf@dhapc248.dev.necel.com>

Hi,

On 8/20/07, Miles Bader <miles.bader@necel.com> wrote:
> dhruva <dhruvakm@gmail.com> writes:
> > I am quite prejudiced when it comes to using CYGWIN.
>
> What does that mean??

Having used MKS toolkit and MinGW, I personally feel they are much
faster as they do not need an emulation layer (based on limited usage
and knowledge). Even AT&T UWIN out performed other equivalents. The
fork implementation in UWIN was far superior (similar to MS-SFU).

-dky

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!

  reply	other threads:[~2007-08-20  6:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 15:59 Info about available CVS/Arch/Git branches Stefan Monnier
2007-08-09 20:57 ` Reiner Steib
2007-08-12  3:45 ` Michael Olson
2007-08-12  9:10   ` Andreas Schwab
2007-08-13  9:42     ` David Kastrup
2007-08-13 10:06       ` Jim Meyering
2007-08-13 10:21         ` David Kastrup
2007-08-13 10:52           ` dhruva
2007-08-13 11:05             ` David Kastrup
2007-08-18  9:20             ` Andreas Schwab
2007-08-18 10:39               ` dhruva
2007-08-20  4:22                 ` Miles Bader
2007-08-20  6:12                   ` dhruva [this message]
2007-08-13 11:50           ` Jim Meyering
2007-08-13 13:05             ` Andreas Schwab
2007-08-13 13:07               ` Jim Meyering
2007-08-13 13:28                 ` Randal L. Schwartz
2007-08-13 14:46                   ` Jim Meyering
2007-08-13 16:41                     ` Jim Meyering
2007-08-13 14:32       ` Andreas Schwab

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=e3f230850708192312i41f3ec5ex2dae33d0b0556a41@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.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).